Module 6
Microservices Architecture
Learn to design distributed systems: service decomposition, API gateways, event-driven patterns, and building resilient services.
0%
Microservices Architecture
API Gateway routing to independent services with message queue and service mesh.
Breaking a monolith into microservices requires careful boundary identification.
Domain-Driven Design (DDD)
Identify bounded contexts - areas where a particular model applies.
Example E-commerce Domains:
•User Management (auth, profiles)
•Product Catalog (items, categories)
•Order Management (cart, checkout)
•Payment Processing (transactions)
•Shipping (logistics, tracking)
•Notifications (email, push)
Decomposition Strategies:
By Business Capability
Align services with what the business does:
•"Payment Service" handles all payment logic
By Subdomain
Core, Supporting, Generic subdomains:
•Core: Competitive advantage (recommendation engine)
•Supporting: Necessary but not differentiating (user auth)
•Generic: Can be outsourced (email sending)
Signs You've Split Wrong:
•Services constantly calling each other
•Distributed transactions everywhere
•High coupling between services
•Data duplication causing inconsistencies
Right Size for Microservices:
•Can be rewritten in 2 weeks
•Single team can own it
•Has clear API boundaries
•Deployable independently
Interactive: Hover over services
Each service is independently deployable