How to Make a Platform Delightful, or Avito PaaS After Five Years
summary
Avito describes the evolution of its internal PaaS over five years, focusing on making the developer platform more convenient. The talk covers problems caused by teams adopting DevOps and owning full lifecycle work, and explains platform-level solutions and practices Avito implemented to reduce overhead for teams (internal PaaS design, tooling and operational changes).
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:08DevOps and team ownership
- 2:30Self-service platform
- 3:12Decision zoo problem
- 5:15Unification and tech radar
- 6:40Service configuration
- 9:11Complexity hiding
- 9:53Low adoption problem
- 12:22Unified dev pipeline
- 15:33Misuse cases
- 17:40Misuse-resistant platform
- 20:10Incident navigation
- 21:54Resource efficiency
- 23:16Platform architecture
- 26:27Summary
- 27:52Q&A
related talks
46mHappiness as a Service — a platform and growth from ten developers to three hundred in three years
29mIaC Next Steps in Platform Engineering
33mPlatform as a Product - Transforming from Service Delivery into Continuous Operations
06mKeynote: PlatformOps: It’s all about Developer Experience
41mPlatform Engineering for Developers, Architects & the Rest of Us
33mPlatform engineering: Build your own PaaS
37mAchieving High Performance with an Internal Developer Platform
39mPlatform Engineering as a (Community) Service