Architecting Cloud Native Microservices
summary
Seven-step methodology lays out concrete choices: define domain objects and SLAs (500 ms target, 99.99% availability), model with schema.org and OData, create a facade and API Gateway, use OAuth/SAML/JWT and threat modeling, apply circuit breakers and fail‑fast behavior, and version APIs with contract tests (PACT). An e‑commerce prototype (Zoomazon) shows Kafka streams → Spark → Elasticsearch for recommendations, active‑user caching in Redis cache, and third‑party protection with Kafka stream retries and OData partial responses.
AI-written summary · about
chapters (17)
- 0:00Introduction to methodology
- 3:13Amazon.com assignment overview
- 7:23Fixing monolithic API anti-patterns
- 10:10API design principles KISS YAGNI
- 14:23Semantic descriptors and state diagrams
- 17:54Bounded context and swim lanes
- 20:21Micro formats and OData standards
- 24:18Universal and common data models
- 29:17Empathy maps and persona-based design
- 33:53Uber case study and scalability
- 37:24Micro service integration challenges
- 41:03Circuit breakers and fail-fast patterns
- 43:27Staggerfit and aggregation patterns
- 46:41Cancellation and CQRS patterns
- 48:06Hurricane throttling strategy
- 50:33Multi-tenant e-commerce architecture
- 55:10Summary and Q&A
related talks
51mExploring Stateful Microservices in the Cloud Native World
26mCreating a scalable ecosystem of Microservices
51mCompetitive retail architecture with microservices
08mThe Evolution of Microservices Architecture in Cloud-Native
16mMicroservices Paradise: is it possible to achieve?
48mCloud Native Java
34mArchitektury Aplikacji: The last mile of microservices
28mThe journey from monolith to microservices