Packaging And Deploying 5 Java Frameworks in 5 Ways
summary
Five frameworks (Micronaut, Quarkus, Spring Boot, Ratpack, Spark Java) get packaged as fat jars or native binaries, container images built with Maven/Jib or Docker, pushed to Azure Container Registry, and deployed to App Service, Container Instances or AKS with kubectl apply. Quarkus compiles to a GraalVM native image and runs as a native container; Micronaut and Spark use Jib to push images; Kubernetes setup and secrets/provisioning prove slow and brittle, while Container Instances and App Service deploys are fast and working.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:12Why these talk
- 1:46Azor support
- 2:00Where do services run
- 3:16Java EE API
- 6:12Spring
- 7:07Quercus
- 9:15Code
- 9:37Ratpack
- 12:10Ratpack Code
- 13:47Wetpack
- 18:49Terraform
- 20:45Dashboard
- 20:58Kubernetes Cluster
- 22:00Kubernetes Microservice
- 26:45Maven Build
- 28:19Accessing Application
- 29:06Port Configuration
- 33:09Container Instance
- 36:09App Service
- 41:06Spring Boot
- 47:31Web App for Containers
related talks
36mJava: The new wave of Java web frameworks
30mBattle Of The Microservice Frameworks: Micronaut versus Quarkus edition!
01h 06m2020 - A space odyssey with Micronaut and Quarkus
30mSupersonic Java Quarkus with Knative serverless
46m5 Ways to Make Java Development and Kubernetes Spark Joy With Quarkus.
28mPackaging & Deployment Options for Scala Applications / Services
44mQuarkus: Supersonic, Subatomic Full-Stack Development
47mJava App Development in the Cloud: MicroProfile, Quarkus and Cloud.