Creating a scalable ecosystem of Microservices
summary
Top 10 pragmatic rules for scaling microservices with concrete examples: avoid the data model library anti-pattern — never let other services import your DB schema; use API gateways for auth and rate limits but keep business logic out, or deploy a sidecar service mesh; prefer async with dead‑letter queues for multi‑step onboarding (Excel → user → dependents → email); weigh REST/JSON vs gRPC based on team discipline; use ELK, correlation IDs and consumer-driven contract testing (Pact, Spring Cloud Contracts); automate docs with Swagger; enforce TLS and tokens; prevent a distributed monolith as services grow from tens to hundreds.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:00Welcome
- 1:55Domain Driven Design
- 4:00API Gateway
- 5:55Communication Protocols
- 8:25Washing your APIs
- 9:58Performance of services
- 12:15observability maturity
- 14:54testing
- 17:04documentation
- 19:08security
- 21:10building a distributed monolith
- 23:10QA
related talks
24m10 commandments for scalable microservices
26mBuilding Scalable Microservice APIs From The Beginning
45mMicroservices: A retrospective
20mMicroservices Anti-Patterns
49mChallenges in Implementing Microservices
25mMaking microservices a behaviour not a buzzword
45mResponsible Microservices
40m10 tips for failing at microservices