Managing Lifecycle of Microservices at Scale
summary
Companies moving from monoliths to microservices face concrete governance gaps so the talk describes building an identity service that issues canonical identifiers, a credential manager for secrets, a metadata manager tied to Teletraan, a centralized resource manager, and a metering/ chargeback system (Kite-style). Pinterest cites 75 billion pins and Twitter cites 2,000+ services and ~200,000 containers; these systems replace brittle spreadsheets, restore ownership visibility, enable capacity planning, and measurably cut waste and operator toil.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:15Agenda
- 1:48What is Pinterest
- 4:57Microservices at Pinterest
- 7:26Benefits of Microservices
- 9:00Microservices enable organizations to scale
- 9:17Things are not always what they seem
- 9:30What is a job
- 10:46What is the release phase
- 14:46Governance is needed
- 16:10Simple service example
- 17:34Who owns
- 19:32Provisioning identifiers
- 26:25Defining primitives
- 33:54Conclusion
related talks
27mTinkertoys, Microservices, and Feature Management: How to Build for the Future
39mGetting started with internal open source
43mStandardizing Microservice Development
08mWhy we are writing a monolith, not a microservice
26mThe Wonders of Onboarding: The Ultimate API Management Adventure
46mBuilding on spring boot lastminute.com microservices way
46mSimplifying Microservices: The art of effortless development
02h 42mEasy microservices with JHipster