blog: announce grpc-zero #2390
blog: announce grpc-zero #2390
Conversation
|
🎊 PR Preview c98d24a has been successfully built and deployed to https://quarkus-site-pr-2390-preview.surge.sh
|
| == TL;DR | ||
|
|
||
| Quarkus gRPC Zero brings gRPC code generation into the JVM so you no longer need native 'protoc' binaries. Add the extension, build your project, and the generated stubs appear just like before. | ||
| The important outcome is consistent, portable builds across developer machines, CI, containers, and even unusual architectures. |
There was a problem hiding this comment.
I'd add a line break here so it stands up as a paragraph.
_posts/2025-09-05-grpc-zero.adoc
Outdated
|
|
||
| == Why this matters | ||
|
|
||
| If you have spent time wrestling with platform-specific 'protoc' binaries, cross-compiled plugins, or flaky CI images, you know the cost: slow onboarding, fragile builds, extra Docker layers, and ongoing maintenance. Quarkus gRPC Zero removes that operational burden so teams can focus on APIs and features instead of shipping native binaries for every target OS and architecture. |
There was a problem hiding this comment.
protoc (to have fixed-width font)
_posts/2025-09-05-grpc-zero.adoc
Outdated
| == What Quarkus gRPC Zero does | ||
|
|
||
| Quarkus gRPC Zero runs the `protoc` compilation inside the JVM as a pure Java codegen step. | ||
| From a developer point of view nothing changes: you keep writing '.proto' files, run your Quarkus build, and use the generated sources. |
_posts/2025-09-05-grpc-zero.adoc
Outdated
| From a developer point of view nothing changes: you keep writing '.proto' files, run your Quarkus build, and use the generated sources. | ||
| The difference is that builds are portable and predictable on any JVM host. | ||
|
|
||
| == Benefits you will see |
_posts/2025-09-05-grpc-zero.adoc
Outdated
|
|
||
| == Current status and roadmap | ||
|
|
||
| Quarkus gRPC Zero is ready for early adopters. |
There was a problem hiding this comment.
I'd put a line break after that sentence.
_posts/2025-09-05-grpc-zero.adoc
Outdated
|
|
||
| == Closing | ||
|
|
||
| Quarkus gRPC Zero is about outcomes: consistent builds and no more native 'protoc' maintenance. |
|
Thanks @jponge for the review! |
|
Ready for final review, optimistically set the publication date to this Friday 🤞 |
|
@andreaTP could you update the dates of both the file name and the preamble and I think we can merge? |
|
(I let you do it in case you don't want to publish on a Friday :)) |
|
Thanks @gsmet ! Just give me a date somewhere next week 🙂 |
|
Tentatively updated the date to tomorrow. |
|
@cescoffier @jponge who should I coordinate with to make this happen? |
|
@andreaTP I will have a look on my trip back tomorrow. |
_posts/2025-09-30-grpc-zero.adoc
Outdated
| == Benefits | ||
|
|
||
| * Portable builds that behave the same on laptops, CI, containers, and edge devices. | ||
| * Simpler CI and smaller images because you do not need to package native executables. |
There was a problem hiding this comment.
No that's not true, it does not change the size fo the artifact, only the amount of dependency you download.
_posts/2025-09-30-grpc-zero.adoc
Outdated
|
|
||
| Outcome: the developer ergonomics are unchanged, but there are no native tools to manage. | ||
|
|
||
| == When to choose this extension |
There was a problem hiding this comment.
I would remove that section.
There was a problem hiding this comment.
Can we have a "Behind the curtain" section instead mentioning WASM, and Chicory?
There was a problem hiding this comment.
applied both suggestions
_posts/2025-09-30-grpc-zero.adoc
Outdated
| We want real-world feedback and we especially want to hear about any errors, edge cases, or surprising behavior you encounter. | ||
| We are happy to quickly to turn things around to fix outstanding bugs. | ||
|
|
||
| * Clone or add the extension to a test project. |
There was a problem hiding this comment.
I would only keep the last bullet point:
Report an issue on ....
Co-authored-by: Clement Escoffier <[email protected]>
Co-authored-by: Clement Escoffier <[email protected]>
Co-authored-by: Clement Escoffier <[email protected]>
Co-authored-by: Clement Escoffier <[email protected]>
Co-authored-by: Clement Escoffier <[email protected]>
Co-authored-by: Clement Escoffier <[email protected]>
Co-authored-by: Clement Escoffier <[email protected]>
Co-authored-by: Clement Escoffier <[email protected]>
|
@cescoffier I believe I addressed all the comments, I changed the date to next Tue, let me know how it reads now. |
4 participants
Blog post announcing gRPC Zero availability as experimental.
cc. @alesj @cescoffier @jponge