Skip to content

Commit b1bc00b

Browse files
committed
review
1 parent 96b112f commit b1bc00b

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

_posts/2025-09-05-grpc-zero.adoc

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,19 +14,22 @@ author: andreatp
1414
== TL;DR
1515
1616
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+
1718
The important outcome is consistent, portable builds across developer machines, CI, containers, and even unusual architectures.
1819
1920
== Why this matters
2021
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.
2223
2324
== What Quarkus gRPC Zero does
2425
2526
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+
2730
The difference is that builds are portable and predictable on any JVM host.
2831
29-
== Benefits you will see
32+
== Benefits
3033
3134
* Portable builds that behave the same on laptops, CI, containers, and edge devices.
3235
* 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
6568
== Current status and roadmap
6669
6770
Quarkus gRPC Zero is ready for early adopters.
71+
6872
It passes integration tests and works in typical Quarkus builds.
6973
We are actively improving the project and welcome feedback, real-world testing, and bug reports to guide stabilization and future features.
7074
@@ -82,5 +86,5 @@ We are happy to quickly to turn things around to fix outstanding bugs.
8286
8387
== Closing
8488
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.
8690
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

Comments
 (0)