Untangling the Tangled Cloud
summary
Practical method for organizing cloud accounts by measuring actual inter-project dependencies rather than handwaving principles: an open-source tool called Ferent (written in Clojure) scans Google Cloud projects, counts service-account permissions to infer edges, and reports cycles and an instability score (outbound / total links). Example run analyzes 44 projects, finds cycles and surprising cross-project couplings, and produces actionable targets for regrouping projects into low-coupling, high-cohesion units.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:54Dependency graphs and boundaries
- 5:09Tangled cloud case studies
- 8:59Pain points of unorganized resources
- 13:14Solving with boundaries
- 16:02Tools for boundaries
- 20:57Organizing dimensions and labels
- 22:46Boundary pitfalls
- 24:30Conway’s law and alignment
- 27:20Minimizing cycles and coupling
- 28:24Low coupling high cohesion
- 31:01Stability and change
- 33:10Measuring instability
- 35:18Introducing fair-in tool
- 39:10How fair-in works
- 41:18Key takeaways
related talks
48mCloud Chaos & Microservices Mayhem
43mWalking on Broken Clouds
46mMeet the Social Side of Your Architecture
05mFive Minute Cost-Optimisation
17mCloudscape: A Study of Storage Services in Modern Cloud Architectures
23mDon't Stop at the Cloud - Connecting all the Dots with Infrastructure-as-Code
21mCloud-Based Contextual Analysis as Code
20mAtomics Habits in cost optimizations in the cloud