-
Notifications
You must be signed in to change notification settings - Fork 394
blog: announce grpc-zero #2390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
blog: announce grpc-zero #2390
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,98 @@ | ||
--- | ||
layout: post | ||
title: 'Quarkus gRPC Zero' | ||
date: 2025-10-16 | ||
tags: quarkus grpc | ||
synopsis: 'gRPC code generation that runs on the JVM so you do not need native protoc binaries.' | ||
author: andreatp | ||
------------------- | ||
|
||
= Quarkus gRPC Zero | ||
|
||
*Make gRPC code generation portable: no native protoc, no surprises.* | ||
|
||
== 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. | ||
|
||
== Why this matters | ||
|
||
If you have spent time wrestling with platform-specific `protoc` binaries, cross-compiled plugins, 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 trying to find the right combination of dependencies to compile `proto` files. | ||
|
||
== What Quarkus gRPC Zero does | ||
|
||
Quarkus gRPC Zero runs the `protoc` compilation inside the JVM as a pure Quarkus _codegen_ module. | ||
|
||
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. It avoids having to download dozen of dependencies to handle every OS/architecture combination. | ||
|
||
== Benefits | ||
|
||
* Portable builds that behave the same on laptops, CI, containers, and edge devices. | ||
* Simpler CI and less downloads as you don't need native executables. | ||
* Less maintenance for platform teams who no longer manage platform-specific toolchains. | ||
* A small, self-contained Java dependency that performs `proto` file compilation. | ||
|
||
== Quick start | ||
|
||
Add the extension to your project. Replace 'VERSION' with the release you choose. | ||
|
||
[source,xml] | ||
---- | ||
<dependency> | ||
<groupId>io.quarkus</groupId> | ||
<artifactId>quarkus-grpc</artifactId> | ||
<exclusions> | ||
<exclusion> | ||
<groupId>io.quarkus</groupId> | ||
<artifactId>quarkus-grpc-codegen</artifactId> | ||
</exclusion> | ||
</exclusions> | ||
</dependency> | ||
<dependency> | ||
<groupId>io.quarkiverse.grpc.zero</groupId> | ||
<artifactId>quarkus-grpc-zero</artifactId> | ||
<version>VERSION</version> | ||
</dependency> | ||
---- | ||
|
||
If you are migrating from an existing Quarkus gRPC setup, you need to exclude the 'quarkus-grpc-codegen' artifact from your 'quarkus-grpc' dependency and add 'quarkus-grpc-zero' instead as a drop-in replacement. | ||
Build your project as usual and generated sources will appear during the build step. | ||
|
||
== Example workflow | ||
|
||
. Add the 'quarkus-grpc' dependency with exclusions for 'quarkus-grpc-codegen' and include 'quarkus-grpc-zero'. | ||
. Keep authoring '.proto' files as before. | ||
. Run the Quarkus build. Generated stubs will be produced on the JVM and compilation completes normally. | ||
|
||
The developer ergonomics are unchanged, but there are no native tools invoked during the process. | ||
|
||
== Current status and roadmap | ||
|
||
Quarkus gRPC Zero is currently experimental but ready for early adopters. | ||
|
||
It passes integration tests and works in typical Quarkus builds. | ||
We are actively improving the project and welcome feedback, real-world testing, and bug reports to guide stabilization and future features. | ||
|
||
== Under the Hood | ||
|
||
The extension embeds a version of `libprotobuf`, compiled to WebAssembly (with the CLI stripped out) and translated into pure Java bytecode thanks to https://chicory.dev[Chicory]. | ||
The result is a self-contained JAR that provides the full `protoc` engine capabilities (including plugin support) and runs on any JVM, transparently and portably across platforms. | ||
|
||
== Try it and report any errors | ||
|
||
Please try Quarkus gRPC Zero in your projects. | ||
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. | ||
|
||
If you see an error, open a ticket at the project repository: https://github.com/quarkiverse/quarkus-grpc-zero/issues[quarkiverse/quarkus-grpc-zero issues] | ||
|
||
Your reports will shape the project and help us make code generation reliable for everyone. | ||
|
||
== Closing | ||
|
||
Quarkus gRPC Zero is about outcomes: consistent builds and no more native `protoc` maintenance. | ||
Try it, use it in your CI, and please report any feedback so we can make it production-ready for every environment. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect!