Microservices Patterns

The craft of decomposing systems into independent services and making them work reliably together. Covers decomposition strategies, communication patterns, data ownership, and the resilience patterns that keep a distributed system from cascading into total failure.

When to Use

Use for:

• Deciding whether to decompose a monolith and where to start
• Designing service boundaries using bounded contexts and domain-driven design
• Choosing between synchronous (REST/gRPC) and asynchronous (events) communication
• Implementing saga pattern for distributed transactions
• Designing API gateways and backend-for-frontend (BFF) layers
• Applying circuit breaker, bulkhead, and retry patterns
• Event sourcing and CQRS design
• Service discovery and load balancing strategies

NOT for:

• Monolith internal architecture (use database-design-patterns, api-architect)
• Serverless function design and deployment