This whitepaper contains additional guidance not found in the SaaS Lens of the AWS Well-Architected Tool.
Hardware patterns
| SaaS SUS 2: How do you maximize the value from the resources that the SaaS environment consumes? |
|---|
SaaS, by its nature, tries to promote the sharing of infrastructure across tenants to maximize efficiency and economies of scale. SaaS providers should continually evaluate their opportunities to maximize infrastructure sharing to promote reduced energy consumption. SaaS providers should have an iterative improvement process that allows them to identify opportunities to limit excess resource consumption.
-
Best Practice–01: Use managed services to shift the responsibility for maintaining optimal utilization of the deployed hardware to AWS.
-
Best Practice–02: Right-size compute resources based on your architecture and iteratively optimize by tracking utilization, and use auto-scaling to handle peak system load.
-
Best Practice–03: Use serverless computing and other managed services to automatically scale resources as needed, eliminates tasks for infrastructure provisioning and management, and resources utilization is optimized.
AWS services recommendation:
-
AWS Compute Optimizer analyzes the configuration and utilization metrics of your AWS resources. It reports whether your resources are optimal, and generates optimization recommendations.
-
Amazon CloudWatch metrics provide data about the performance of your system, for example, CPU utilization.
-
Auto Scaling—AWS provides multiple services that you can use to scale your application.
-
Examples of AWS managed services:
-
Serverless on AWS
helps you build and run applications without thinking about servers, capacity sizing and provisioning, and maintenance.
