Microservices on Java EE — As Cool As The LHC
summary
Java EE runs as tiny deployables and fast containers: builds push only a Thin WAR (often ~3KB–500KB) while the app‑server image stays stable, so incremental Docker pushes to Docker + ECS take seconds after the first upload. Cold starts are ~1.5–3s on Tomcat/Payara/WildFly, a simple benchmark hits ~1,500 TPS, and app‑server features (exposed via 4848 monitoring) surface bean pool counts and latencies. Robustness uses managed executor service for bulkheads and async, circuit‑breaker logic via simple AOP, and CI/CD is Jenkins pipelines that run unit, integration and stress stages.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:11How To Achieve a Good Time to Market
- 7:21What We Need for Setup
- 12:31What Do You Get for Free Is Monitoring
- 18:47Docker File
- 31:13Jenkins File
- 40:31Logging
- 42:47How To Communicate between Microservices
- 44:38Load Balancing
related talks
42mCloud Native Java EE
01h 00mRefactor your Java EE application using Microservices and Containers
35mOptimize your applications to the max with Jakarta EE and MicroProfile
45m12-Factor, Cloud Native Enterprise Java Applications
41mThe Slideless Microservices Session
41mBuilding Low Latency Microservices & Monoliths in Java
49mSupersonic subatomic Enterprise Java from the ground up
48mSupersonic, Subatomic Eclipse MicroProfile
