Monolith to Microservices
summary
ADP runs a huge HCM platform with ~490,000 cloud clients, ~35M active users and ~5M logins a day (peak ~19,000/s), and is converting a single organized monolith to microservices by incremental strangling the monolith and lift‑and‑shift extraction. Engineering moves to separate repos, client libraries, contract testing and CI that produces immutable containers. Tooling includes Docker, Nginx, Consul, Swagger, Vagrant, Jenkins, AWS/GCE/OpenStack and orchestration like Swarm/Mesos/Kubernetes. Outcome so far: ~20 services now, >60 planned; guiding principles are promises and tests.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:34Agenda
- 2:02ATP at Scale
- 4:56Organized Monolith
- 6:14The Bad
- 8:08Conways Law
- 9:10Stangulation
- 16:19Promises
- 19:10Lift Shift
- 21:38Microservice Quantification
- 22:36Clients
- 24:19Testing
- 25:42Enabling Microservices
- 28:39Conclusion
related talks
42mQ&A - Monolith to Microservices
38mFrom Monolith to Microservices at Zalando
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
57mSplitting Monolith Application to Microservices
25mFrom Millions of Customers to Petabytes of Data: A Journey to Microservices
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
48mMicroMonolith
30mMonolith-ifying perfectly good microservices
