Please enable JavaScript.
Coggle requires JavaScript to display documents.
Microservices - Coggle Diagram
Microservices
Service Decomposition & Domain Modeling
✅ Expected to Know
How to identify service boundaries using Domain-Driven Design (DDD)
When to split or merge services
Tradeoffs between modular monoliths and microservices
✅ Patterns
Bounded Contexts from DDD
Self-contained Systems
Strangler Fig for legacy migration
✅ Best Practices
Align service boundaries with business domains
Avoid entity services (e.g., UserService, ProductService as anemic)
Use event storming and context mapping workshops
❌ Anti-Patterns
“Nano-services”: splitting services too small for no good reason
Sharing databases across services
Communication & Integration
✅ Expected to Know
When to use REST, gRPC, or event-driven communication
Managing synchronous vs. asynchronous tradeoffs
✅ Patterns
API Gateway for central access
Backend for Frontend (BFF) for client-specific APIs
Event-Driven Architecture with pub/sub (Kafka, SNS+SQS, EventBridge)
✅ Best Practices
Prefer async messaging for non-blocking workflows
❌ Anti-Patterns
Data Management & Consistency
✅ Expected to Know
✅ Patterns
✅ Best Practices
❌ Anti-Patterns
Service Discovery & Load Balancing
✅ Expected to Know
✅ Patterns
✅ Best Practices
Deployment & Lifecycle
✅ Expected to Know
✅ Patterns
✅ Best Practices
Observability (Monitoring, Logging, Tracing)
✅ Expected to Know
✅ Patterns
✅ Best Practices
Security & Governance
✅ Expected to Know
✅ Patterns
✅ Best Practices
Resilience & Fault Tolerance
✅ Expected to Know
✅ Patterns
✅ Best Practices
Team Topology & Ownership
✅ Expected to Know
✅ Patterns✅ Patterns
✅ Best Practices
Platform Engineering & Enablement
✅ Expected to Know
✅ Patterns
✅ Best Practices
Migration Strategy
✅ Patterns
✅ Expected to Know
✅ Best Practices