From VMs to Containers: Decompose and Migrate Old Applications
summary
Argues that after decomposing a ten‑year legacy into services, moving from VMs to containers cuts cost and speeds scaling, demonstrates a working migration: VZ containers running a GlassFish cluster connected to a database, deployed from a template and scaled up to replicas (example shows 20), cloned for CI/CD, and migrated live using live migration (CRIU). Claims orchestration (Kubernetes/Mesosphere/Tectonic/Jelastic) handles health checks, load balancing and automatic provisioning so the app runs correctly and more efficiently than on VMs.
AI-written summary · about
chapters (20)
- 0:00Introduction to migration
- 1:10Legacy application environments
- 2:38Hosting evolution from bare metal
- 4:29Why containers matter today
- 5:52Container isolation basics
- 8:06Container benefits over VMs
- 10:14Cost efficiency with containers
- 12:27Scaling strategies explained
- 15:23Templates and provisioning
- 17:18CI/CD with containers
- 18:50One service per container
- 20:17GlassFish migration example
- 23:52Live migration advantages
- 24:56Automating resource scaling
- 26:22Orchestration tools overview
- 27:30Practical demo setup
- 31:06Smart vs stupid containers
- 32:10Traffic distribution and failover
- 34:00Avoid reinventing the wheel
- 35:05Modernizing legacy systems
related talks
36mDeploying an Application Across Multiple Clouds
24mMicroservices and Containers. How much faster than a VM?!
22mEVOLUTION OF CLOUD NATIVE INFRASTRUCTURE
23mMicroservices and containers
25mContainers as an enabler for microservices and what it means for our industry
10mThe differences between microservices and containers
26mThe Journey to Microservice Adoption
01h 04mDeploying and Scaling Microservices