5 quick tips to make your Java apps more awesome
summary
Five concrete practices and a working demo: build a Jakarta EE/MicroProfile service with fault tolerance (timeouts, retries, circuit breaker, bulkheads) that fails over to a backup endpoint when a flaky backend (dice-roll failure) trips, expose health probes (liveness/readiness/startup) and /metrics for Prometheus, use feature toggles via Unleash to flip features in ~10 seconds, and manage infra as code (Terraform/Pulumi) for reproducible Kubernetes deployments; demo runs as four containers and the failover/toggle behavior works.
AI-written summary · about
chapters (10)
- 0:00Welcome and introduction
- 1:54Concepts vs code
- 3:15Jakarta EE and MicroProfile
- 6:23Fault tolerance in apps
- 10:56Health checks explained
- 13:23Metrics and monitoring
- 14:27Feature toggling benefits
- 18:44Infrastructure as code
- 20:55Live demos
- 24:29Summary and thanks
related talks
51m5 Tips to Make Your Java Apps More Awesome!
59m5 tips to make your Java apps more awesome. Non-functional Requirements Exemplified
52mBulletproof Java Enterprise Applications for The Hard Production Life
55m10 strategies for developing reliable Jakarta EE & MicroProfile apps for the Cloud
01h 00mBulletproof Java Enterprise applications for the hard production life
29mHow to develop your first cloud-native Applications with Java
01h 21mTips, Tricks and Workarounds with Jakarta EE/MicroProfile
40m6 tips for your JavaEE project be less depressing
