Jakarta EE + MicroProfile: The Nonfunctional Features #slideless.
summary
Builds two Quarkus MicroProfile services (a slow responder and a client) and wires up Health liveness/readiness probes, Metrics exposed to Prometheus, and bulkhead with fallback plus retry for fault tolerance. Uses MicroProfile Rest Client, java.util.logging, and auto-generated OpenAPI/Swagger UI. Demonstrates bulkhead limiting to one concurrent execution, causing ~97,000 fallback calls under load, shows per-status counters created at runtime, and uses WebApplicationException to return custom HTTP statuses. Everything runs live in dev mode and Prometheus scraping and alerts are shown working.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 3:37About the speaker and Jakarta EE
- 7:26Demo setup and MicroProfile overview
- 12:06Metrics and logging in MicroProfile
- 17:22Health checks and probes
- 26:59Fault tolerance with bulkhead
- 33:28REST client and retry mechanisms
- 39:19Exception handling with Jakarta
- 43:36OpenAPI and Swagger UI
- 45:23Q&A and closing remarks
related talks
47mDream Team Jakarta EE + MicroProfile
36mPractical Cloud Native Java Development with MicroProfile
42mMicroProfile: microservices made easy
57mA New and Open Way to Build Cloud-Native Microservices - MicroProfile
01h 07mJava EE Meets Microservices: MicroProfile 2.x to the Rescue
01h 21mTips, Tricks and Workarounds with Jakarta EE/MicroProfile
50mBuilding reactive microservices with MicroProfile
45mEnd to End Portable Microservices - with Eclipse MicroProfile
