You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2025-09-05-grpc-zero.adoc
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,19 +14,22 @@ author: andreatp
14
14
== TL;DR
15
15
16
16
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.
17
+
17
18
The important outcome is consistent, portable builds across developer machines, CI, containers, and even unusual architectures.
18
19
19
20
== Why this matters
20
21
21
-
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.
22
+
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.
22
23
23
24
== What Quarkus gRPC Zero does
24
25
25
26
Quarkus gRPC Zero runs the `protoc` compilation inside the JVM as a pure Java codegen step.
26
-
From a developer point of view nothing changes: you keep writing '.proto' files, run your Quarkus build, and use the generated sources.
27
+
28
+
From a developer point of view nothing changes: you keep writing `.proto` files, run your Quarkus build, and use the generated sources.
29
+
27
30
The difference is that builds are portable and predictable on any JVM host.
28
31
29
-
== Benefits you will see
32
+
== Benefits
30
33
31
34
* Portable builds that behave the same on laptops, CI, containers, and edge devices.
32
35
* Simpler CI and smaller images because you do not need to package native executables.
@@ -65,6 +68,7 @@ Outcome: the developer ergonomics are unchanged, but there are no native tools t
65
68
== Current status and roadmap
66
69
67
70
Quarkus gRPC Zero is ready for early adopters.
71
+
68
72
It passes integration tests and works in typical Quarkus builds.
69
73
We are actively improving the project and welcome feedback, real-world testing, and bug reports to guide stabilization and future features.
70
74
@@ -82,5 +86,5 @@ We are happy to quickly to turn things around to fix outstanding bugs.
82
86
83
87
== Closing
84
88
85
-
Quarkus gRPC Zero is about outcomes: consistent builds and no more native 'protoc' maintenance.
89
+
Quarkus gRPC Zero is about outcomes: consistent builds and no more native `protoc` maintenance.
86
90
Try it, use it in your CI, and please report any feedback so we can make it production-ready for every environment.
0 commit comments