From Heroku to Cloud Native in 7 Weeks
summary
Soho House moves 40+ apps off Heroku to a reproducible multi‑cloud Kubernetes platform in seven weeks by choosing Kubernetes, Prometheus, Fluentd and automating builds and releases with Helm, drone.io, Third Party Resources, nats.io. CI builds switch from CircleCI to drone to handle large Docker images; Helm releases encapsulate charts and rollbacks; NATS decouples operators/controllers so namespace provisioning, DB creation and Terraform jobs run as cluster jobs. Monitoring is hosted (Cortex) and logging uses Fluentd/CloudWatch; emphasis on health checks and resource limits.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:14Getting into communities
- 8:34Deployments
- 11:34Operators
- 13:07Decouple Components
- 15:42Tools and People
- 17:29Adoption
- 18:07Change is hard
- 18:56Health checks
- 20:09Limits
- 21:10Black boxes
- 21:54Bugs
related talks
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
01h 29mTutorial: Build Your Own Heroku With Cloud Native Stack
28mIf You Know Heroku, You Can Use Kubernetes
35mKubernetes journey
36mPractical Cloud Native: What Works, What Doesn't
22m10 Kubernetes is hard!
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
49mApplications architecture spanning multiple clouds