Building Scalable Microservice APIs From The Beginning
summary
Claims that microservices must scale independently and cohesively with scaling on three axes: functional decomposition (y), horizontal duplication (x) and data partitioning (z). Recommends an API Gateway for single-entry, gateway aggregation and offloaded token auth (OAuth2/OpenID), plus service discovery/routing; uses pub/sub messaging (RabbitMQ, Solace) for async comms and a sidecar service mesh for resiliency, observability and load balancing. Enforces per-service databases for eventual consistency, circuit breakers, small two-person teams, and deploys via Docker, cloud, serverless or on‑prem.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:23Scaling Software
- 4:18Gateway Design Pattern
- 8:50PubSubsystems
- 9:45Service Mesh
- 12:05Best Practices
- 18:18TokenBased Authentication
- 19:55Deployment Options
- 20:45Questions
related talks
26mCreating a scalable ecosystem of Microservices
45mMicroservices: A retrospective
23mMicroservice Security at the API Level
43mGo micro with Microservices
29mImpact of Microservices Architecture on API Management
20mMicroservices Anti-Patterns
36mDo Proper Monoliths before You Do Microservices!
52mBeyond Microservices: Streams, State and Scalability