How we did Platform Engineering at Datadog
summary
Defines platform engineering as a real product line that moved Datadog from scattered product-owned tooling to a centralized core org, uses Terraform, Kubernetes and lots of open source, and introduces a three-phase model that actually shipped: scrappy to scalable to robust. The org shifts from hybrid product teams to a core platform team with 500–700 engineers under management, funds headcount to stop one-off forks, accepts added TPMs and change management, and finds coherence improves reliability though politics and bureaucracy persist.
AI-written summary · about
chapters (7)
- 0:00Introduction and Background
- 0:49Defining Platform Engineering
- 2:21The Evolution of Platform Engineering: Promises, Complexity and Challenges
- 7:39Organizational Structure at Datadog
- 15:36Transitioning from Scrappy to Scalable to Robust Platforms
- 20:50Conclusion
- 21:40Q&A
related talks
49mFrom DevSecOps to Platform Engineering
41mPlatform Engineering for Developers, Architects & the Rest of Us
29mIaC Next Steps in Platform Engineering
45mPlatform Engineering: A Deep Dive Conversation
15mThe Art of Platform Engineering
22mDevOps vs Platform Engineering: Navigating the Path Ahead
39mPlatform Engineering as a (Community) Service
28mWhat to Expect from Your Application Platform