Refactor your Java EE application using Microservices and Containers
summary
Shows a concrete path to refactor a Java EE monolith by convert WAR to EAR to isolate functional modules, extract those modules as independent WARs on WildFly, then package each as a Docker image per service and run them with containers. Recommends separate databases per service, Nexus for artifacts, Hystrix-like circuit breakers for resiliency, and Kubernetes for orchestration using the Kubernetes desired state model. Cites Netflix scale (roughly 33% peak traffic, ~2 billion API calls mapped to 6–12 internal calls) and demonstrates the approach works and self heals.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:10Monolith architecture overview
- 8:14Issues with monolith applications
- 10:43Microservices characteristics
- 20:04Strategies for decomposition
- 27:07Advantages of microservices
- 32:28Evolutionary refactoring approach
- 38:30Microservices complexity shift
- 44:11Containers and Docker basics
- 52:40Kubernetes orchestration
- 57:14DevOps with Kubernetes
- 1:00:04Q&A and wrap-up
related talks
53mMicroservices on Java EE — As Cool As The LHC
42mCloud Native Java EE
41mContinuous Delivery with Docker Containers and Java EE
01h 22mWebinar: Decomposing Applications for Deployability and Scalability
50mMicroservices Design Patterns for Java Application
54mJava based microservices, containers, Kubernetes - how to
35mDocker, microservices, functional programming (...)
57mSplitting Monolith Application to Microservices