Cloud Native Spring - Migrating Traditional Apps.
summary
Five concrete migration steps: replace external app server with embedded Tomcat and executable JAR (or move to WebFlux or serverless), containerize with Cloud Native Buildpacks (paketo) producing layer jars and Java 11, externalize config via Spring Cloud Config from Git or env vars, make instances disposable with graceful shutdown and 20s timeout, and add observability with Actuator + Micrometer for Prometheus metrics. Demos build images, fetch config, and expose liveness/readiness; the final Kubernetes deploy to three replicas mostly works though the live demo hits a deployment issue.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:15Application Server - Traditional WAR/EAR artifacts deployed to an application server
- 4:09Application Server - Cloud Native
- 11:43Containerization Packaging Spring Boot apps as Docker images
- 12:48Working with Docker Images
- 17:29Code and Configuration
- 17:49Configuration - Traditional Configuration files and environment variables
- 18:50Configuration - Cloud Native
- 27:37Application Lifecycle - Traditional
- 28:38Application Lifecycle - Cloud Native Disposable and stateless applications
- 34:12Health Checks Liveness and readiness probes
- 45:04Cloud Native Spring in Action With Spring Boot and Kubernetes
related talks
55mCloud Native with Spring Boot & Kubernetes
01h 31mRunning Your Spring Apps in the Cloud
52mMicroservices with Java, Spring Boot and Spring Cloud
52mCloud-native streaming and event-driven microservices
01h 02mMigrating from Java EE: to Spring Boot or Something Else
49mKubernetes Native Java
56mKeynote: Kubernetes Native Java
55mSpring, Functions, Serverless and You
