Engineering Culture First: The Journey to Building Sphera, monday.com's IDP
summary
Built a custom Internal Developer Portal called Sphera IDP that centralizes service catalog, deployments, incident triage and secrets, removing CLI and local-machine dependencies. Claims include automating DB and SQS provisioning to reach 100 resources per month, onboarding ~40 microservices and ~20 teams monthly, and supporting an org that pushes 30,000 code changes per month across 500 microservices and 2M req/s. CI/CD, built‑in monitoring, feature‑flags and rollbacks live in the portal; visibility and developer autonomy improve while full end‑to‑end automation is still a work in progress.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:49Monday.com’s growth and challenges
- 3:59Transition from monolith to microservices
- 6:27Early tooling and its limitations
- 7:31Building Sphera as an IDP
- 9:40Sphera’s architecture and team ownership
- 10:46Automating developer workflows
- 12:32Adding new features to Sphera
- 14:16Culture and developer autonomy
related talks
44mBeyond Metrics: Orchestrating Developer Delight with AI driven Platform Engineering
11mBuilding Scalable Developer Platforms
20mPlatform Engineering XXL
38mOur adventure in building an internal developer platform
15mDeveloper portal
29mIaC Next Steps in Platform Engineering
44mPlatform Engineering 101: Building Internal Developer Platforms
22mPlatform Engineering at bol
