Updates to the Performance Efficiency pillar of the AWS Well-Architected Framework

AWS recently published a significant update to the AWS Well-Architected Framework, and as part of that update, the Performance Efficiency Pillar whitepaper has been streamlined and improved. The questions in the whitepaper are now better aligned with those in the AWS Well-Architected Tool, making it easy to cross-reference between them when reviewing workloads. With clearer headings and each best practice highlighted, you can quickly find what you need and then dive deep on any topic.

AWS also updated the Performance Efficiency pillar to reflect the evolution of AWS and the best practices we are seeing in the field. In each best practice, they have added—and in many cases expanded on—these innovations to improve your performance in the cloud. New services, such as the AWS Nitro System, AWS Global Accelerator, AWS Local Zones, and AWS Outposts, can help you achieve this goal.

The Performance Efficiency pillar now describes hybrid networking options, such as the AWS Outposts network setup shown here.

Enterprise environments are often a mix of cloud, on-premises data centers, and edge locations. To address this, AWS modified the networking best practice to include performance considerations for hybrid cloud architectures. AWS also highlights AWS services that can increase your networking performance.

In addition to those changes, they have also added an additional focus to help address common performance bottlenecks in cloud architectures. New explanations are included to help address common situations, such as compute selection, storage selection, and database selection. With database selection, AWS added new information to help you choose between our 15 purpose-built database engines, which include relational, key-value, document, in-memory, graph, time series, and ledger databases. AWS now stresses that performance optimized workloads should pick the best database to solve a specific problem or group of problems, and not simply utilize one-size-fits-all monolithic databases.

Lastly, AWS has included new information regarding performance monitoring. For example, they describe using CloudWatch Synthetics to check the latency of your workload endpoints, AWS X-Ray to capture performance-related metrics, and CloudWatch ServiceLens to integrate traces, metrics, logs, and alarms into one place to measure against critical key performance indicators (KPIs). These services allow you to gain a deeper insight into workload performance and ensure that the services are performing as expected.

This update to the Performance Efficiency pillar of the AWS Well-Architected Framework gives you additional insight into the tools and services needed to continuously improve your workload performance. I encourage you to use the AWS Well-Architected Tool to continually measure and improve your cloud workloads over time, measuring the impact of your performance improvements, and documenting those changes as milestones in the tool.

3 lượt xem0 bình luận

Bài đăng gần đây

Xem tất cả