Performance efficiency patterns
Performance efficiency is the ability of your workload to meet the demands placed on it by users in an efficient manner. You need to anticipate increases in load to meet business requirements. To achieve performance efficiency, it's important to consider how your application scales and to implement platform as a service (PaaS) offerings that have built-in scaling operations.
Performance efficiency depends on the system's ability to handle load increases without impacting performance, or for available resources to be readily increased. Performance efficiency concerns not just compute instances, but other elements such as data storage, messaging infrastructure, and application architecture.
The following table summarizes architectural design patterns that relate to performance efficiency.
| Pattern | Summary |
|---|---|
| Cache-aside | Load data on demand into a cache from a data store. |
| Choreography | Have each component of the system participate in the decision-making process about the workflow of a business transaction, instead of relying on a central point of control. |
| Command query responsibility segregation (CQRS) | Segregate operations that read data from operations that update data by using separate interfaces. |
| Event sourcing | Use an append-only store to record the full series of events that describe actions taken on data in a domain. |
| Deployment stamps | Deploy multiple independent copies of application components, including data stores. |
| Geodes | Deploy backend services into a set of geographical nodes, each of which can service any client request in any region. |
| Index table | Create indexes over the fields in data stores that are frequently referenced by queries. |
| Materialized view | Generate prepopulated views over the data in one or more data stores when the data isn't ideally formatted for a required query. |
| Priority queue | Prioritize requests sent to services so that requests with a higher priority are received and processed more quickly than requests with a lower priority. |
| Queue-based load leveling | Use a queue that acts as a buffer between a task and a service that it invokes in order to smooth intermittent heavy loads. |
| Sharding | Divide a data store into a set of horizontal partitions or shards. |
| Static content hosting | Deploy static content to a cloud-based storage service that can deliver the assets directly to the client. |
| Throttling | Control the consumption of resources used by an instance of an application, an individual tenant, or an entire service. |
Feedback
Submit and view feedback for