Java inside Application Containers, System Containers and VMs
summary
Compares running Java in application containers, system containers and VMs and claims nested containers (application inside system containers, skipping VMs) reduces overhead and increases resource reuse; demonstrates Minecraft live migration with zero downtime across AWS and Azure on the Jelastic platform; describes Jelastic auto-adjusting JVM heap (Xmx set to ~80% of container) but currently requiring container restart while coordinating with OpenJDK to enable live adjustments; notes Java 12 and Java 16 improvements that return unused heap and metaspace and a pay-as-you-use billing model that charges only actual consumption.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:05The Difference between System Containers and Virtual Machines
- 9:03Cross Cloud Deployments
- 10:37Scaling Java inside Vms and inside Containers
- 11:45Horizontal Scaling
- 14:51Direct Memory
- 27:24Difference between the Pay-per-Use and Pay-as-You-Go System
- 28:17Vertical Scaling
- 36:52Automated Installation of Kubernetes
- 42:03Control Panel
- 42:16Cluster Upgrade
related talks
48mJava in Containers - Part Deux
47mLegal JVM Doping in Your Containers
49mJava and Containers Make it Awesome
46mJava in a container: operational specifics
49mThe Diabolical Developer's Guide to JVM Ergonomics in Containers
07mBest Practices with JVMs in Containers
42mA State of Java Elasticity
42mContainers & Java: What I wish I have been told!