Typical Pattern to keep in mind
| Application architecture patterns
|
Cross cutting concerns
|
Microservices Design Patterns
Gateway Aggregation Pattern
This pattern involves using an API gateway to aggregate various microservices into a single endpoint for clients.
Saga Pattern
The saga pattern is used to manage distributed transactions across multiple microservices by orchestrating a sequence of local transactions.
Event Sourcing Pattern
In this pattern, changes to the state of a system are captured as a sequence of events.
CQRS Pattern (Command Query Responsibility Segregation)
CQRS separates the command and query responsibilities, allowing for different models to be optimized for reads and writes.
Service Registry Pattern
This pattern involves using a service registry to keep track of available services in a microservice architecture. It allows services to dynamically discover and communicate with each other.
Circuit Breaker Pattern
The circuit breaker pattern is used to handle failures and prevent cascading failures in a microservice architecture. It provides a mechanism to detect and handle failures in remote service calls.
Event-Driven Architecture
In this pattern, services communicate with each other through events. Events are used to trigger actions and propagate changes across the system. This pattern enables loose coupling and scalability.
Database per Service Pattern
In this pattern, each microservice has its own dedicated database. This allows services to have independent data models and enables better scalability and autonomy.
Distributed Tracing
Distributed tracing is a pattern that allows you to trace requests as they flow through a distributed system. It helps in understanding the performance and behavior of individual microservices.
Health Check API
The health check API pattern involves implementing an API endpoint that provides information about the health of a microservice. It helps in monitoring the availability and status of individual microservices.
Log Aggregation
Log aggregation is a pattern that involves collecting and centralizing logs from multiple microservices. It helps in troubleshooting and analyzing the behavior of the system as a whole.
Audit Logging
Audit logging is a pattern that involves capturing and storing logs for auditing purposes. It helps in tracking and monitoring the activities and changes within a microservice architecture.