Quarkus: gRPC support

[paulrobinson]

Description

Implementing support for gRPC is likely to be a long running task. This Epic is to cover the Minimum Viable Product implementation, so that we can release something useful ASAP and then iterate on it going forwards.

An early task needs to be to decide what should be included in the MVP and to maybe schedule some follow-up Epics for future work.

Analysis

(links to analysis docs containing architecture design work, requirements gathering, etc)

Tasks

• [x] _Checklist of sub tasks goes here, represented as links to GitHub issues_

[sean-scott-lr]

Is there any chance that official support for GRPC in quarkus will end up looking like the PoC here?
https://github.com/quarkusio/quarkus/issues/820

[marziman]

Hello Quarkus-Maintainers (@cescoffier @gsmet @stuartwdouglas),

we are currently working on bringing Quarkus into production.
The missing support for gRPC is outruling many of our services to be used with Quarkus & GraalVM.

Can you please give it a priority? As many folks will do microservices with gRPC, I believe beside us many will be thankful and push Quarkus mission forward.

Also: Big Thank you, guys. You re awesome! Quarkus is next level !

[sean-scott-lr]

We are using https://github.com/hpehl/quarkus-grpc-extension.

We have written a couple interceptors that tie the grpc-server into jwt-RBAC, tracing, metrics, and hibernate-validator...

The only problem we have now is that grpc-client breaks our native image compilation. If someone that understands quarkus extensions and graalvm could finish that up, or if you don't need the client then you are set.

---

From: Mehmet Arziman [e-mail]
Sent: Tuesday, March 10, 2020, 3:18 AM
To: quarkusio/quarkus
Cc: Sean Scott; Manual
Subject: Re: [quarkusio/quarkus] MVP for gRPC support (#5627)

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hello Quarkus-Maintainers,

we are currently working on bringing Quarkus into production.
The missing support for gRPC is outruling many of our services to be used with Quarkus & GraalVM.

Can you please give it a priority? As many folks will do microservices with gRPC, I believe beside us many will be thankful and push Quarkus mission forward.

Also: Big Thank you, guys. You re awesome! Quarkus is next level !

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/quarkusio/quarkus/issues/5627?email_source=notifications&email_token=AMOM7B4E4IOQEH2FVCHIST3RGYAXLA5CNFSM4JPSQFGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOKTTJI#issuecomment-596982181, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMOM7BZKYBIFHJ4VSFKBCVLRGYAXLANCNFSM4JPSQFGA.

[cescoffier]

Work done in https://github.com/quarkusio/quarkus-grpc.
Once the PRs are merged it supports native (Java 11 only because of ALPN).

[cescoffier]

This work has been completed.