Top 10 Microservices Patterns
Mostly used Top 10 Microservices Patterns:
1] API Gateway Pattern
Single entry point for all client requests, which then routes those requests to the appropriate microservice
2] Circuit Breaker
Pattern used to handle failures in a microservices architecture when a microservice fails or becomes unresponsive, the circuit breaker tips and redirects requests to a fallback service
3] Service Registry
Pattern used to keep track of all the services in a microservices architecture. The registry acts as a central directory for service discovery
4] Service Mesh
Pattern that involves adding a layer of infrastructure between microservices to handle cross-cutting concerns such as service discovery, load balancing and security
5] Event Driven Architecture
Pattern that involves using events to communicate between microservices. Each microservices can publish events and subscribe to events published by other microservices.
6] Saga
Pattern used to manage transactions that span multiple microservices. It involves breaking the transaction into smaller, individual steps and using compensating action to undo completed steps if an error occurs.
7] Bulkhead
Pattern used to isolate failure in a microservices architecture. Each microservices is placed in a separate container, so if one microservices fails, it does not affects other microservices.
8] Sidecar
Pattern that involves deploying a separate container alongside each microservices to handle cross cutting concerns such as logging, monitoring and security.
9] CQRS
Pattern that involves separating the read and write model in a microservices architecture. The read model is optimized for querying data, while the write model is optimized for updating data.
10] Strangler
Pattern that involves gradually replacing a monolithic application with microservices by gradually adding new microservices and removing functionality from the monolith.
11] API Composition
13] Retry
14] Configuration Externalization Pattern
15] Leader Election
Comments
Post a Comment