From Legacy to Cloud Native, Without Kubernetes
summary
The talk addresses how large organizations can evolve monolithic, VM-hosted Java application landscapes toward cloud-native architectures without adopting Kubernetes. It outlines a stepwise approach and tools for incrementally adapting on-premises infrastructure and application deployment (e.g., Spring Boot microservices scenarios are referenced) so operations teams can modernize without a multi-year Kubernetes project.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:45Legacy system challenges
- 8:14Domain-driven design
- 12:14Containerization and discovery
- 19:50Automation and CI/CD
- 24:30Security and secrets
- 29:07Reverse proxy and load balancing
- 33:44Service mesh and policies
- 36:57Orchestration with Nomad
- 41:08Container security
- 44:47Four years of modernization
- 47:45Q&A
related talks
46mIt Doesn't Always Have to Be Kubernetes
30mMigrating a monolith to Cloud-Native and the stumbling blocks
25mMigrating a monolith to Cloud-Native and the stumbling blocks that you don’t know about
25mMigrating a monolith to Cloud-Native and the stumbling blocks that you don’t know about.
54mLegacy in a Box: Dev Environment on Kubernetes
32mWhat Cloud Native Java Really Means for Developers
39mYou Don’t Need Kubernetes to Be Cloud Native
06mLightning Talk: Moving away from legacy requires a non-legacy approach!