When to Stop Building Your Own IDP
summary
Company builds an internal IDP called cahi with 50 integrations maintained by a team of seven, which becomes unscalable; decision metrics compare staffing cost, tool sprawl, and time-to-value and lead to a switch to a SaaS IDP — moved to Cortex. Cortex shows usable data within a month, takes six months to migrate integrations, and frees engineers to work on gateways, accelerators and deploy gates while centralizing compliance checks and production metrics.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 3:14Building an internal IDP
- 10:13Why New Zealand builds first
- 12:20Moving away from custom IDP
- 21:09Floating platforms concept
- 24:19Challenges of switching to SAS
- 27:51Outcomes after adopting Cortex
related talks
20mPlatform Engineering XXL
11mBuilding Scalable Developer Platforms
31mBuilding an IDP Using Lego Principles
15mEngineering Culture First: The Journey to Building Sphera, monday.com's IDP
29mIaC Next Steps in Platform Engineering
41mArchitecting Kubernetes-Based Internal Developer Platforms: Essential Patterns...
25mLet’s Go Backstage: End to End IDP Tips & Tricks for Platform Engineers
26mIntel’s Journey to Large Scale DevOps Transformation