JakartaEE and Eclipse MicroProfile coexist in WildFly
summary
WildFly combines full Jakarta EE with Eclipse MicroProfile so a single server runs legacy apps and cloud-native services together; claim: this enables progressive migration rather than full rewrites. MicroProfile supplies concrete APIs — metrics, tracing, retries/fallbacks, REST client and OpenAPI — that add observability and fault tolerance to a monolith. WildFly 19 beta1 already ships MicroProfile support, and real examples include wrapping old JCA connectors as services so legacy integrations stay usable while new microservices take over.
AI-written summary · about
chapters (8)
- 0:00Start
- 15:35Lasagna Architecture
- 21:17Micro Service Architecture
- 21:56What Is a Micro Service or Not
- 25:17Identify Services
- 28:05Progressive Migration
- 32:56Using Other Service with Rest Client
- 43:59Takeaways
related talks
35mMicroProfile and Jakarta EE -- What's Next?
47mDream Team Jakarta EE + MicroProfile
36mPractical Cloud Native Java Development with MicroProfile
51mJakarta EE 10 and Beyond
01h 07mJava EE Meets Microservices: MicroProfile 2.x to the Rescue
36mMicroProfile and Jakarta EE Panel
53mMicroprofile - New and Noteworthy
52mEclipse MicroProfile: A quest for a lightweight and modern enterprise Java platform