RPC Architecture — REST at Boundary, gRPC Inside
📍 Used after slide 34
Loading diagram…
When to use REST vs gRPC architecturally — public API boundary vs internal service mesh.
Speaker Notes
Architectural context: REST at the public API boundary (browsers, partners), gRPC for internal pod-to-pod calls. Quarkus Demo 05 runs both protocols simultaneously on the same service.