Cloud Design Patterns: Compensating Transaction

• Undo the work performed by a series of steps, which together define an eventually consistent operation, if one or more of the operations fails.
• Operations that follow the eventual consistency model are commonly found in cloud-hosted applications that implement complex business processes and workflows.

When to use

• Use this pattern only for operations that must be undone if they fail. If possible, design solutions to avoid the complexity of requiring compensating transactions.

Reference

• Documentation: https://docs.microsoft.com/en-us/azure/architecture/patterns/compensating-transaction

Cloud Design Patterns: Circuit Breaker

• Handle faults that may take a variable amount of time to rectify when connecting to a remote service or resource.
• This pattern can improve the stability and resiliency of an application.

When to use

• To prevent an application from trying to invoke a remote service or access a shared resource if this operation is highly likely to fail.

Reference

• Documentation: https://docs.microsoft.com/en-us/azure/architecture/patterns/circuit-breaker

Cloud Design Patterns: Cache-Aside

• Load data on demand into a cache from a data store.
• This pattern can improve performance and also helps to maintain consistency between data held in the cache and the data in the underlying data store.

When to use

• A cache doesn't provide native read-through and write-through operations.
• Resource demand is unpredictable. This pattern enables applications to load data on demand. It makes no assumptions about which data an application will require in advance.

Reference

• Documentation: https://docs.microsoft.com/en-us/azure/architecture/patterns/cache-aside