10 strategies for developing reliable Jakarta EE & MicroProfile apps for the Cloud
summary
Ten concrete practices for running Jakarta EE + MicroProfile services on the cloud: favor statelessness and CDI scopes, avoid EJBs, use JCache or a distributed cache (Payara uses Hazelcast) for shared temporary state, enable JPA second‑level cache with EclipseLink, handle config via MicroProfile Config (env vars, Docker/Kubernetes), apply Fault Tolerance patterns (retry, fallback, bulkhead, circuit breaker, timeout) as CDI interceptors, use JWT propagation for stateless auth, and export metrics to Prometheus/Grafana — examples include a ratings endpoint that falls back to cache when DB writes fail.
AI-written summary · about
chapters (14)
- 0:00Start
- 7:23Eclipse MicroProfile
- 9:25Reliable Clustering
- 12:00Jakarta EE - Distribution
- 13:58Filling the Gaps
- 15:28No Silver Bullets
- 16:37Statelessness
- 21:49– "True" Singleton
- 31:47CDI EJB
- 39:05Strategy #6 - JPA Caching
- 42:37Fault Tolerance
- 48:33Stateless Security
- 51:41Metrics
- 54:05More Resources
related talks
36mPractical Cloud Native Java Development with MicroProfile
01h 21mTips, Tricks and Workarounds with Jakarta EE/MicroProfile
50mJakarta EE 10: Modern & Lightweight Cloud Application Development
47mDream Team Jakarta EE + MicroProfile
51m5 Tips to Make Your Java Apps More Awesome!
35mOptimize your applications to the max with Jakarta EE and MicroProfile
55mModern and Lightweight Cloud Application Development with Jakarta EE10
35mMicroProfile and Jakarta EE -- What's Next?