Embracing Cloud Native at a Thriving, Established Company
summary
MailChimp migrates a 17‑shard PHP monolith toward microservices by running Kubernetes clusters on bare metal, managing clusters with Puppet, and integrating Flannel, HAProxy, Helm (as templated manifests), Jenkins, Artifactory, and a Pando CLI. Prometheus + Alertmanager handle app metrics, sealed secrets use sealed-secrets, and an early cluster hits a capacity bug where ~1,300 CPU cores are fully requested; the log pipeline moves to k8s (about 95% stateless) while devs keep local parity via NFS PVs. Continued experiments include Envoy/service‑mesh work.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:18About Brian
- 0:54About MailChimp
- 1:44What does MailChimp do
- 2:09MailChimp is hiring
- 2:28Shoutout to Team Panda
- 3:09Specific to the context
- 3:42MailChimp Architecture
- 5:10MailChimp Services
- 5:55Multiple Instances
- 7:52Deployer
- 9:05Engineering Expectations
- 10:33Why Change
- 14:47How to Get There
- 15:01The Real World
- 15:12Kubernetes Deployment
- 16:33MailChimp Networking Scheme
- 17:25Kubernetes Components
- 18:46External Authentication
- 20:38Integration
- 24:13Ingress
- 28:00Developer Experience
- 30:39Metrics
- 32:14Chat
- 33:26Latebreaking
- 34:53Future work
- 35:03Business critical apps
- 36:13Service mesh
related talks
45mHow Kubernetes Was the Secret Sauce in Our Globally Distributed Team’s Transition to Microservices
23mThe Nine Journey: Cloud Native Transformation
28m"Building the Plane While It's Flying"
30mMigrating a monolith to Cloud-Native and the stumbling blocks
20mThe path to self-healing: Re-architecting for massive scale on kubernetes
32mKubernetes Namespaces Unleashed: Unlocking the Full Potential of You...
29mK8s Complexity Tamed: One Interface To Rule Them All With CNCF Incubat...
27mLightning Talk: GitOps, A Slightly Realistic Situation on Kubernetes with Flux