ignatandrei
commented
7 months ago - Retry Pattern:
Automatically retry failed operations to improve the chances of success.
- Cache-Aside pattern:
Loading data into a cache on-demand to improve data access times and reduce server load.
- Blue-Green Deployment pattern:
Deploying a new version of an application alongside the old one for easy rollback in case of issues.
- Ambassador pattern:
Proxy managing communication between microservices.
- Backends for Frontends pattern:
Specialized backend services for different user interfaces (frontends).
- Bulkhead pattern:
Isolating components to prevent cascading failures in a system.
- Circuit Breaker pattern:
Limiting requests to prevent system overload during a failure or downtime.
- CQRS pattern:
Separating read and write operations for improved system scalability.
- Event Sourcing pattern:
Capturing and storing every state-changing event for data reconstruction.
- Materialized View pattern:
Precomputing and storing query results for faster data retrieval.
- Publisher-Subscriber pattern:
Communication pattern where senders notify many receivers.
- Rate Limiting pattern:
Restricting the rate of incoming requests to a system.
- Saga pattern:
Coordinating a series of transactions to maintain data consistency.
- Sidecar pattern:
Independent service extends the functionality of a main application.
- Throttling pattern:
Controlling the rate of processing to prevent resource exhaustion.
Build reliable and scalable applications by studying proven cloud design patterns.
https://substack.com/@systemdesignone/note/c-54451197