This feature is experimental.

The Java/Scala API’s to enable this feature may still change in further versions of Akka gRPC, and future versions of this feature may not work with services generated with older versions of Akka gRPC.

There may be missing features and bugs in the current implementation. If you encounter any, you are welcome to share a reproducer in our issue tracker.

gRPC cannot be used directly from the browser because of limitations on the amount of control the Javascript code has on the behavior of the browser.

The gRPC-Web protocol was designed to be usable from a browser, but be easily translatable into native gRPC calls.

The most common deployment model of gRPC-Web is to use a proxy such as Envoy to translate between the gRPC-Web frontend and a native gRPC back-end. This is a great choice with Akka gRPC services.

However, in some situations it may be operationally simpler if your service supports gRPC-Web directly. This is now possible with Akka gRPC as well.

To serve a gRPC service with Akka gRPC, it is recommended to serve the native gRPC protocol on a different port than gRPC-Web, as the two protocols will likely require a different security story. You can use WebHandler.grpcWebHandlerWebHandler.grpcWebHandler to serve your gRPC-Web endpoint with basic CORS infrastructure in place. To use CORS please have a look at our akka-http docs.

And then serve the handlers with WebHandler.grpcWebHandlerWebHandler.grpcWebHandler like this:

sourceimport akka.grpc.scaladsl.WebHandler

val grpcWebServiceHandlers = WebHandler.grpcWebHandler(greeterService, echoService)

  .newServerAt("", 8081)
sourceimport akka.grpc.javadsl.WebHandler;

Function<HttpRequest, CompletionStage<HttpResponse>> grpcWebServiceHandlers =
    WebHandler.grpcWebHandler(Arrays.asList(greeterService, echoService), sys, mat);

  .newServerAt("", 8090)
Found an error in this documentation? The source code for this page can be found here. Please feel free to edit and contribute a pull request.