You've heard of Fat/Uber JARs and are probably building them today. They provide much greater app portability and minimize the risk of missing dependencies. However, in a containerized world, where small code changes and re-deployments can occur frequently for high scale environments, the overhead of processing and transferring virtually duplicate content can quickly grow. In this session, we'll explore the benefits and costs of Fat JAR packaging and demonstrate various options for slimming your apps and saving those trees using popular frameworks like Wildfly Swarm, Dropwizard, Spring Boot and Eclipse Vert.x.
2. Fat JARs
• Easily Portable, easily runnable (esp. in IDEs)
• Dependencies resolved at build time (not in production)
• Everyone supports it
• Dropwizard was first (March 2011)
• Everything in one JAR
• Everything in one container layer
• Fat JAR is rebuilt for single line change