gRPC Meets Jakarta EE - Ron Sigal, Red Hat
summary
WildFly now accepts a dropped JAR that contains an io.grpc.BindableService and registers it with a WildFly gRPC subsystem so the service runs with full Jakarta EE facilities; RESTEasy scans Jakarta REST resource classes with JavaParser, generates a .proto (faking packages with underscores, embedding supertypes via _super fields and using google.protobuf.Any for interface returns), and ships intermediary classes that build servlet requests/responses and pack/unpack messages. A resteasy-grpc maven archetype automates the generation and supports server‑streaming.
AI-written summary · about
chapters (9)
- 0:00Jakarta EE and gRPC intro
- 3:54Why gRPC matters
- 6:18gRPC clients to REST apps
- 9:33Protobuf from Java classes
- 12:45gRPC and REST translation
- 14:11RESTEasy gRPC projects
- 19:29gRPC-Jakarta EE use cases
- 20:37Reactive streaming support
- 23:03Q&A
related talks
53mJakartaEE and Eclipse MicroProfile coexist in WildFly
52mPimp your Jakarta EE applications
45mEverything YOU need to Know About Jakarta EE 10
55mModern and Lightweight Cloud Application Development with Jakarta EE10
33mJava EE Microservices with WildFly Swarm
43mEleventh Time's the Charm - From J2EE to Jakarta 11
40mJakarta EE 10 - Simplicity for Modern and Lighweight Cloud Applications
26mA Brokerless REST Interface for gRPC Services