There are several key trade-offs to consider while using Docker and Kubernetes with Jakarta EE applications. Examples include:
- Whether to use thin WARs, fat JARs, or hollow uber-JARs to effectively work with Docker repositories, layering, and caching.
- Whether to deploy applications within images, through exposed admin ports or as autodeployed mounted external volumes.
- How Docker networking and Kubernetes cluster deployments align with application server administration, clustering, auto-discovery, and load-balancing.
- How the CI/CD pipeline of your application can be adapted to Docker and Kubernetes.
This entirely slide-less, fast-paced, demo-driven session walks through each of these considerations
Slides (External URL):
Objective of the presentation:
This slide-free session explores key trade-offs to consider while using Docker and Kubernetes effectively with Jakarta EE applications.
Attendee pre-requisites - If none, enter "N/A":