Taming software sprawl and demystifying your distributed architecture (PRT032)
summary
Companies see a 29% drop in high-performing teams as component counts balloon from single-app modernizations into hundreds of microservices and small portfolios hit thousands of components. Engineers spend ~30% of their time just looking for ownership and docs, and 56% report security processes slowing delivery. The remedy shown is a concrete toolset: a centralized Compass catalog with decentralized ownership, an activity feed for upstream events to cut MTTR, and automated scorecards to enforce compliance during delivery.
AI-written summary · about
chapters (6)
- 0:00Introduction to software sprawl
- 2:12What is software sprawl?
- 3:35Symptom one multiple post-incident reviews
- 7:14Symptom two busy unproductive teams
- 10:46Symptom three governance bottleneck
- 13:39Solutions and key takeaways
related talks
01h 02mTools for simplified large scale systems
18mPatching Your Way to Compliance with a Small Team and a Pile of Technical Debt
59mDecomposition Patterns
50mTactics and strategies on software development: how to reach ...
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
38mConway's law in practice: Agile teams & Microservises
33mFrom Enterprise Architecture to Software Design - Critical Thinking
01h 26mChaos Development: Removing Software as the Inhibitor of Agile