Time Complexity: Why AWS Well-Architected matters
O(n)
0
0
Why AWS Well-Architected matters - Performance Analysis
Understanding Time Complexity
We want to understand how the effort to review and improve cloud setups grows as the system gets bigger.
How does the time to check and fix architecture scale with more resources?
Scenario Under Consideration
Analyze the time complexity of reviewing multiple AWS resources using the Well-Architected Tool.
aws wellarchitected list-lenses
aws wellarchitected list-milestones --workload-id workload123
aws wellarchitected list-review-summaries --workload-id workload123
aws wellarchitected get-workload --workload-id workload123
aws wellarchitected list-workloads
This sequence fetches details and reviews for a workload to check its architecture quality.
Identify Repeating Operations
Identify the API calls, resource provisioning, data transfers that repeat.
- Primary operation: Listing and fetching details of workloads and their reviews.
- How many times: Once per workload or per review item, depending on the number of resources.
How Execution Grows With Input
As the number of workloads grows, the number of API calls grows roughly in direct proportion.
| Input Size (n) | Approx. Api Calls/Operations |
|---|---|
| 10 | About 10 to 50 calls |
| 100 | About 100 to 500 calls |
| 1000 | About 1000 to 5000 calls |
Pattern observation: The effort grows linearly as you add more workloads to review.
Final Time Complexity
Time Complexity: O(n)
This means the time to review scales directly with the number of workloads you have.
Common Mistake
[X] Wrong: "Reviewing more workloads takes the same time as reviewing one."
[OK] Correct: Each workload adds more checks and data to process, so time grows with the number of workloads.
Interview Connect
Understanding how review time grows helps you plan and manage cloud projects better, a useful skill in real work.
Self-Check
"What if we automated some review steps? How would the time complexity change?"