// Topics / AWS
AWS
Definition
AWS coverage in this archive spans 11 posts from Mar 2016 to Dec 2021 and focuses on reliability, delivery speed, and cost discipline as one system, not three separate concerns. The strongest adjacent threads are cloud, architecture, and infrastructure. Recurring title motifs include cloud, bill, aws, and terraform.
Key claims
- Most posts prioritize predictable operations over feature breadth or stack novelty.
- Early posts lean on cost and cloud, while newer posts lean on cloud and bill as constraints shifted.
- This topic repeatedly intersects with cloud, architecture, and infrastructure, so design choices here rarely stand alone.
Practical checklist
- Set SLOs first, then choose tooling that keeps deploy, observability, and rollback simple.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read cloud and architecture before committing implementation details.
Failure modes
- Adding platform layers faster than the team can operate and debug them.
- Chasing throughput gains without proving they improve end-user reliability.
- Applying guidance from 2016 to 2021 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): The AWS us-east-1 Outage Was Predictable. Your Architecture Was Not Ready.
- Then read (operating middle): Your Cloud Bill Is a Design Document
- Finish with (foundational context): AWS Lambda: When Serverless Makes Sense (And When It Doesn’t)
Related posts
- The AWS us-east-1 Outage Was Predictable. Your Architecture Was Not Ready.
- Terraform at Scale: What Changed Since 2019
- Multi-Cloud Is Mostly a Marketing Strategy
- Serverless vs Containers: Where the Math Stops Working
- Your Cloud Security Is Falling Apart Right Now
- Your Cloud Bill Is a Design Document
- Your Cloud Bill Is Lying to You: A Cost Optimization Comparison
- Your Cloud Bill Is Lying to You
References
11 entries tagged “AWS”