Zendesk’s Cloud‑Native Transformation: Migrating to Kubernetes and Microservices
The article details how Zendesk modernized its monolithic Rails architecture by adopting Docker, microservices, and Kubernetes, building internal tools like ZDI and Samson, and achieving faster deployments, automated scaling, and improved resilience, with about 70% of its applications now running on Kubernetes.
Zendesk, founded in 2007 as a monolithic Rails application backed by MySQL, grew to over 145,000 paid accounts and needed to modernize its infrastructure. The legacy on‑premise data center caused slow deployments, high operational overhead, and inconsistent environments between staging and production.
Challenge: Scaling the single‑tenant Rails app was becoming untenable; the central ops team required long lead times for hardware provisioning, and extensive Chef scripts created divergent configurations across environments.
Solution: In late 2014 the engineering team evaluated container technologies, adopted Docker, and spent six months developing best‑practice microservice patterns. They created the “ZDI” (Zendesk Docker Integration) tool to spin up containers quickly, but soon realized they needed a proper orchestrator. By summer 2015 they selected Kubernetes, migrated workloads to about 15 AWS clusters, and by early 2017 had production traffic on Kubernetes. New services are now built directly for Kubernetes, resulting in roughly 70% of Zendesk’s applications running on the platform.
“Kubernetes seemed to be built to solve our problems.” – Jon Moter, Senior Principal Engineer, Zendesk
The team also enhanced their open‑source deployment tool Samson to integrate with multiple Kubernetes clusters, read YAML manifests from GitHub, and adjust replica counts, CPU, and RAM via a UI before calling the Kubernetes API. This reduced resource‑change cycles from days to 1‑2 minutes.
Operational benefits include rapid self‑healing during AWS outages (issues resolved in minutes without manual intervention) and a unified orchestration platform that standardizes tooling, monitoring, and alerting across globally distributed teams.
To help other organizations adopt Kubernetes, Moter advises building internal expertise, starting with small applications, and gradually scaling up, while recognizing the learning curve and the need for a dedicated team familiar with the platform.
Business Impact: Resource‑change time dropped from days to minutes, incident recovery now takes minutes instead of hours, and 70% of applications run on Kubernetes, delivering greater flexibility, speed, and reliability for Zendesk’s services.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Cloud Native Technology Community
The Cloud Native Technology Community, part of the CNBPA Cloud Native Technology Practice Alliance, focuses on evangelizing cutting‑edge cloud‑native technologies and practical implementations. It shares in‑depth content, case studies, and event/meetup information on containers, Kubernetes, DevOps, Service Mesh, and other cloud‑native tech, along with updates from the CNBPA alliance.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
