Register or log in to access this video
A case study on taming extreme tech sprawl of 90 K8s clusters, 11 databases technologies, 4 SDLCs. I’ll share how our ‘One PR, One YAML’ tool, Orchestra, created one golden path to operational leverage.
How does tech sprawl happen? You wake up one day to find your organisation is running 90 Kubernetes clusters, supporting 11 different database technologies, and trying to manage 4 distinct, incompatible SDLCs. That was our reality. This is the case study of Dojo’s journey from chaos to centralisation.
The cost of this sprawl was enormous: disparate security implementations and reliability practices, and a developer experience full of friction. This talk details our “”Platform Leap”” on a strategic initiative to centralise by building the Dojo Creator Platform and treating our internal platform as a first-class product.
The catalyst for success was Orchestra: our ‘One PR, One YAML’ workload specification and CLI. This single, self-service abstraction became our “”golden path.”” It allowed us to enforce reliability, quality, and security standards by design, not by committee.
This platform leap solved our sprawl problem and delivered immense operational leverage. By enabling true self-service, we allowed our engineering organisation to scale, delivering more features with less friction and without a linear increase in platform team overhead.
Key takeaways
- Learn how to quantify and communicate the high cost of tech sprawl (e.g., “90 clusters”).
- See how a ‘One PR, One YAML’ abstraction (Orchestra) can drive platform adoption and developer self-service.
- Understand how to enforce “golden paths” to consolidate sprawl and measurably improve reliability and security.
- Gain a blueprint for achieving true operational leverage and scaling your engineering org efficiently.
