// Topics / Cloud
Cloud
Definition
Cloud coverage in this archive spans 22 posts from Mar 2016 to Dec 2022 and focuses on reliability, delivery speed, and cost discipline as one system, not three separate concerns. The strongest adjacent threads are infrastructure, aws, and architecture. Recurring title motifs include cloud, bill, serverless, and patterns.
Key claims
- Most posts prioritize predictable operations over feature breadth or stack novelty.
- Early posts lean on serverless and doesn, while newer posts lean on cloud and bill as constraints shifted.
- This topic repeatedly intersects with infrastructure, aws, and architecture, 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 infrastructure and aws 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 2022 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): Your Cloud Bill Is Not a Mystery
- Then read (operating middle): Your Terraform Monolith Will Break. Here’s How to Fix It Before It Does.
- Finish with (foundational context): AWS Lambda: When Serverless Makes Sense (And When It Doesn’t)
Related posts
- Your Cloud Bill Is Not a Mystery
- Infrastructure as Code Patterns That Actually Scale
- You Do Not Need a FinOps Team
- The AWS us-east-1 Outage Was Predictable. Your Architecture Was Not Ready.
- Terraform at Scale: What Changed Since 2019
- Your Kubernetes Bill Is Lying to You
- Multi-Cloud Is Mostly a Marketing Strategy
- Rust for Cloud Services: A Go Developer’s Honest Take
References
22 entries tagged “Cloud”