Aggregator Pattern
The Aggregator Pattern provides a way for a client to obtain combinations of data from each microservice of a microservice-based application. However it is not exactly the same as an API Gateway.
API Gateway Pattern
The API Gateway Pattern provides a way for a client to obtain combinations of data from each microservice of a microservice-based application.
Proxy Pattern
Problem Statement When upgrading from a monolithic architecture to a microservice-based architecture, the designer(s) can encounter situations where one service depends upon another. Upgrading the dependency can potentially disrupt the service, and in an extreme situation, the entire system, and possibly affect the development of the system. The solution to this problem is the Proxy
Bulkhead Pattern
The bulkhead pattern enforces the principle of damage containment and provides a higher degree of resilience by partitioning the system.
Throttling
The throttling pattern is used to allow a service to maintain a steady pace when process multiple customer requests. Throttling can be implemented using multiple strategies: •Rejecting requests from an individual user who has already accessed the service more than n times over a given period of time. •Disabling or degrading the functionality of selected nonessential services
Circuit Breaker
The Circuit Breaker pattern is used to check the availability of an external service, detect failures and prevent them from happening constantly. For example, if an application needs to retrieve data from an external service 100 times per second, and the service is unavailable (e.g., down for maintain ace or because of a hardware failure),