The Thorns of Containerized Applications and Microservices
summary
Booking.com describes its evolution through three generations of private cloud platforms: an early Mesos/Marathon deployment (used about six months), a year-long OpenShift attempt, and the current deployment on plain Kubernetes. The talk explains the problems encountered with each approach and why the team migrated to and now operates on Kubernetes.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:00Faster deployment demand
- 6:28Manual server challenges
- 7:11Three platform phases
- 8:22Container registry struggles
- 10:08OpenShift adoption issues
- 15:30Support and failures
- 17:38Major platform problems
- 20:52User integration issues
- 26:32Trust loss and recovery
- 29:41Kubernetes design
- 34:56Networking and monitoring
- 39:52Platform achievements
- 41:16Lessons learned
- 42:40Future plans
- 43:20Q&A
related talks
49mDeveloping microservices applications on the Kubernetes platform
48mFrom Monolith to Micro-services with Kubernetes
46mAround & After Kubernetes: The Principles and Ideas that Guide Us
39mTales from Lastminute.com Machine Room: Our Journey Towards a Full On-Premise Kubernetes
34mBringing 1976 into 2016: Ticketmaster’s Public Cloud and Kubernetes Strategy
35mKubernetes journey
46mKeep Building Fresh: Shopify's Journey to Kubernetes
05mBare Metal to Containers to K8s: How We Got Here