Modernize Legacy Systems with Kubernetes
summary
Describes using Kubernetes and CNCF tools to incrementally modernize legacy systems by treating APIs as products, adopting evolutive architectures, and applying CQRS/event-driven fast data with CDC into a message broker, read-model aggregators, and command executors that write back to legacy systems. Gives concrete Kubernetes patterns (pods, sidecars, namespaces, RBAC, CI/CD, monitoring) and a rollout recipe: run a vertical experiment, automate it, then extend; emphasizes it can take years but recommends a measurable business case within ~12–18 months and cites a real bug that doubled networking costs for months.
AI-written summary · about
chapters (11)
- 0:00Modernizing legacy systems
- 2:27Legacy systems defined
- 6:42Guiding principles
- 9:32Why Kubernetes works
- 13:32Kubernetes basics
- 16:19Modern architectures
- 19:29Decoupling with events
- 24:55Handling writes and commands
- 27:02Cultural change
- 29:08Gradual modernization
- 31:15Q&A
related talks
39mUsing Kubernetes to Change Legacy Systems and Processes in the Public Sector
20mApplication Modernization: From Concept to Kubernetes
39mStrangling the Legacy with Kubernetes
14mLessons from the Kubernetes Adventure
54mTransform a Legacy Application with Kubernetes and Istio
19mKube Me This! Kubernetes Ideas and Best Practices
26mAchieving Cloud-Native Resiliency: The Evolution of Chaos Engineering
16mModernizing a legacy app using Windows Containers and Kubernetes: Challenges and Lessons learned
