Running Java Applications on Cloud Foundry
summary
The Java Buildpack performs staging with detect/compile/release scripts, pulls dependencies from an HTTP index, and produces a droplet plus a long tuned command line; it auto-installs a JRE, container (Java main or Tomcat) and optional frameworks like New Relic without app changes. The standout is the memory calculator that accounts for five JVM regions (heap, metaspace, stacks, direct, code cache), assumes a 240 MB code cache and yields ~350 MB heap in a 1 GB container, and refuses containers below ~600 MB.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:35I do not care how
- 2:21Application
- 3:39Staging
- 3:52Build Packs
- 6:25Staging Output
- 7:28Java Build Pack
- 9:17Repository
- 11:27Default Configuration
- 15:42Memory Calculator
- 17:46JVM Memory Calculator
- 24:01Containers
- 24:28Java Main
- 24:52Tomcat Container
- 26:31Frameworks
- 26:55Integration
- 27:23New Relic
- 28:03Container Security Provider
- 28:46Debugger
- 29:11Profilers
- 29:44Create Command Line
- 30:19Outro
related talks
51mJava applications containerized and deployed, make your buildpack edition
37mJava Microservices at Scale on Cloud Foundry, Today and Tomorrow
46mDockerfiles, Buildpacks, Jib and more, best way to run Java code in Containers?
32mJava Buildpack in 2017
47mLegal JVM Doping in Your Containers
01h 00mHow Fit Is Java for the Cloud?
49mDockerfiles, Jib ..., what's the best way to run your Java code in Containers?
43mBuilding containers without DockerFile