From Monolith to Microservices at Zalando
summary
Zalando moves from a Java/Postgres monolith (after outgrowing Magento PHP) to hundreds of microservices, reorganizing into autonomous teams of ~2–12 people (ideal 6) under “radical agility.” Operational stack uses AWS, Docker and Stups IO for provisioning, AppDynamics and custom Zmon/Zetom2 for monitoring, API-first with Place Swagger, router in Go and a Node layout service called Tailor that streams page fragments (BigPipe style). Results: new mobile checkout runs in Italy/Poland with no major incidents, faster onboarding, independent deploys, but auth, monitoring and data‑protection take significant effort.
AI-written summary · about
chapters (13)
- 0:00Introduction and context
- 1:07Company profile and scale
- 2:34Early days and challenges
- 5:13Monolith limitations
- 11:01Radical agility framework
- 16:46Aligning tech with culture
- 18:08Operational challenges
- 20:21Mindset and responsibility
- 23:26Architecture and governance
- 26:11Compliance and security
- 28:12Frontend microservices
- 30:26Benefits and results
- 31:32Future outlook and Q&A
related talks
01mMicroservices Day London | David O'Donoghue, Zalando
41mBuilding and running applications at scale in
23mOn the road from Monolith to Micro
30mMonolith to Microservices
57mSplitting Monolith Application to Microservices
51mCompetitive retail architecture with microservices
03mZalando session at react-europe 2015
43mBreak Up the Monolith: Testing Microservices