Cloud Design Patterns

Nothing here yet.

• Chatty I/OMany small network or database calls where one bigger one would do.
• Competing ConsumersSeveral workers pulling from one queue to share the load.
• External Configuration StoreKeeping configuration in a central service instead of in deploy packages.
• Over-FetchingRetrieving far more data than an operation needs.

• AmbassadorA helper proxy that handles networking concerns for a service.
• Busy DatabasePushing too much processing into the database.
• Claim CheckPutting a large payload in storage and sending only a reference through the queue.
• GatekeeperA dedicated host that validates requests before they reach trusted services.
• Gateway AggregationOne gateway call that fans out to many services and combines the results.
• Gateway OffloadingMoving TLS, auth and other shared concerns into the gateway.
• Index TableA separate table that indexes data by a field the main store can't query efficiently.
• Noisy NeighborOne tenant or workload hogging shared resources and slowing others down.
• Priority Queue PatternProcessing urgent messages before others.
• Queue-Based Load LevelingA queue absorbing traffic spikes so a service sees steady load.
• Scheduler Agent SupervisorCoordinating a multi-step job and recovering steps that fail.
• Sequential ConvoyProcessing related messages in order while unrelated ones run in parallel.

• Deployment StampsDeploying many independent copies of a whole system, e.g. one per region or customer group.
• GeodesServing any request from any region, with data replicated everywhere.

Nothing here yet.

Nothing here yet.

• Chatty I/OMany small network or database calls where one bigger one would do.
• Over-FetchingRetrieving far more data than an operation needs.

• Gateway AggregationOne gateway call that fans out to many services and combines the results.

Nothing here yet.

Nothing here yet.