microservices-patterns

Service decomposition identifies domain-aligned boundaries and contracts to reduce coupling. It enables independent deployment and clear data ownership across services by defining precise communication protocols and isolating domain logic into separate, scalable units.

The saga pattern coordinates distributed transactions across microservices to maintain data consistency without a shared database. You need sagas for distributed data management when services require reliable, multi-step workflows and rollback capabilities across independent service boundaries.

Circuit breakers improve resilience in distributed systems by monitoring communication failures and halting requests to struggling services. This prevents cascading failures across microservices, allowing degraded services to recover while maintaining overall system availability.

Use event-driven architecture for asynchronous communication when you need loose coupling and independent scalability. Synchronous messaging suits immediate request-response needs, while event-driven interactions via event buses support resilient, decoupled processing across distributed systems.

An API gateway orchestrates synchronous and asynchronous messaging between clients and internal services. It provides a unified entry point for routing requests, managing communication patterns, and shielding internal service boundaries from direct client exposure in distributed architectures.

The database per service pattern limits cross-service queries and complicates distributed data management. While it enforces clear data ownership and independent scalability, it necessitates implementing sagas and event-driven communication to maintain consistency without traditional joins.