REL01-BP03 Accommodate fixed service quotas and constraints
through architecture
Be aware of unchangeable service quotas and physical resources, and architect to prevent these from impacting reliability.
Examples include network bandwidth, AWS Lambda payload size, throttle burst rate for API Gateway, and concurrent user connections to an Amazon Redshift cluster.
Common anti-patterns:
-
Performing benchmarking for too short of time, utilizing the burst limit, but then expecting the service to perform at that capacity for sustained periods.
-
Choosing a design that uses one resource of a service per user or customer, unaware that there are design constraints that will cause this design to fail as you scale.
Benefits of establishing this best practice: Tracking fixed quotes in AWS services and constraints in other parts of your workload, such as connectivity constraints, IP address constraints, and constraints in third-party services, allows you to detect when you are trending toward a quota and gives you the ability to address the quota before it's exceeded.
Level of risk exposed if this best practice is not established: Medium
Implementation guidance
-
Be aware of fixed service quotas Be aware of fixed service quotas and constraints and architect around these.
Resources
Related documents:
Related videos:
