#pattern

Pattern providing a single entry point for multiple microservices, handling routing, authentication, rate limiting, and response aggregation.

Architectural pattern where each client type has its own dedicated backend adapting microservice APIs to that client's specific needs.

Pattern for managing distributed transactions in microservices through a sequence of local transactions with compensating actions to handle failures.

Incremental migration strategy that gradually replaces a legacy system with new components, progressively routing traffic until the old system can be retired.