Platform Engineering Decision Framework
summary
Decision criteria: claims, tools, measured outcomes. The talk lays out Kubernetes and service mesh plus CI/CD, distributed tracing and Symfony plugins, cites 30–40% cost savings from granular scaling and 5–10x higher deployment frequency, and contrasts monolith benefits like 50% faster onboarding and in‑process calls 100× faster. Migration timelines appear: full microservices 18–24 months versus monolith optimization 6–12 months. A case study reports deployments 3× faster, code‑to‑prod 21×, uptime +8.5% and MTTR halved.
AI-written summary · about
chapters (11)
- 0:00Introduction and Welcome
- 0:14Microservices vs. Monolith: The Big Decision
- 1:47Deep Dive into Microservices
- 3:13Challenges of Microservices
- 4:28Microservices and DevOps Integration
- 5:38Exploring Monolithic Architecture
- 6:31When to Choose Monolith
- 7:49Making the Right Architectural Decision
- 11:01Real-World Example: Transitioning to Microservices
- 12:52Future Trends in Architecture
- 13:57Key Takeaways and Conclusion
related talks
26mEnhance System Resilience and Efficiency with Microservices
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
32mSplitting the monolith
20mMicroservices in the future
37mKnee Deep in Microservices
26mPivoting your Pipeline from Monolithic to Microservices
27mArchitecting for Change Debate
43mThe Business Implications of Microservices