From monolith to Cloud Native
summary
Engineering Workbench migrates from a monolith to cloud‑native by extracting controller groups into independent microservices, using Docker and Kubernetes for cloud‑agnostic deployment, templates and semver to standardize new services, and CI/CD with canary deploys with automated rollback to reduce release risk. Teams reorganize into vertical cross‑functional squads and guilds, adopt semantic logging and ML alerts for monitoring, and serve 50,000 customers across 140 countries with faster, more stable releases.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:25Migration first steps
- 11:14Team organization and guilds
- 18:06Development training and culture
- 23:48Infrastructure and microservices
- 27:25Automation and deployment
- 32:47Summary
related talks
25mMigrating a monolith to Cloud-Native and the stumbling blocks that you don’t know about
43mMigrating a Mission Critical Monolith to a #CloudNative Architecture
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
28mThe journey from monolith to microservices
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
36mPractical Cloud Native: What Works, What Doesn't
44mMigrating a Monolith to Kubernetes
32mSplitting the monolith