gRPC Remote Procedure Call (with Protobuf) – Grape Up

gRPC Remote Procedure Call (with Protobuf) – Grape Up

A person of the most essential technical decisions during creating API is to pick out the correct protocol for interchanging knowledge. It is not an effortless undertaking. You have to remedy at least a couple of critical queries – which will integrate with API, if you have any network limits, what is the sum and frequency of phone calls, and will the degree of your organization’s technological maturity permit you to keep this in the upcoming?

When you gather all the info, you can examine distinct systems to decide on a single that matches you very best. You can decide and opt for among effectively-known Soap, Relaxation, or GraphQL. But in this posting, we would like to introduce quite a new player in the microservices earth – gRPC Distant Technique Contact.

What is gRPC (Distant Treatment Call)?

gRPC is a cross-platform open up-source Remote Method Get in touch with (RPC) framework in the beginning developed by Google. The platform employs Protocol Buffers as a data serialization protocol, as the binary format necessitates less sources and messages are lesser. Also, a agreement in between the shopper and server is described in proto format, so code can be instantly produced. The framework relies on HTTP/2 (supports TLS) and over and above functionality, interoperability, and code era features streaming capabilities and channels.

Declaring approaches in deal

Have you read through our article about serializing details with Protocol Buffers? We are heading to increase some extra definitions there:

message SearchRequest 
  string vin = 1
  google.protobuf.Timestamp from = 2
  google.protobuf.Timestamp to = 3

information SearchResponse 
  recurring Geolocation geolocations = 1

services GeolocationServer 
  rpc Insert(Geolocation) returns (google.protobuf.Vacant)
  rpc Search(SearchRequest) returns (SearchResponse)

The construction of the file is fairly simple – but there are a couple of points value noticing:

  • company GeolocationServer – assistance is declared by key phrase with that name
  • rpc Insert(Geolocation) – strategies are described by rpc keyword, its title, and request parameter variety
  • returns (google.protobuf.Vacant) – and at the end eventually a return variety. As you can see you have to often return any benefit, in this circumstance, is a wrapper for an vacant structure
  • message SearchResponse recurring Geolocation geolocations = 1 – if you want to return a checklist of objects, you have to mark them as repeated and offer a identify for the field

Establish configuration

We can merge attributes of Spring Boot and simplify the set up of gRPC server by utilizing the devoted library GitHub – yidongnan/grpc-spring-boot-starter: Spring Boot starter module for gRPC framework. (adhere to the installation guide there).

It allow us use all the goodness of the Spring framework (such as Dependency Injection or Annotations).

Now you are ready to crank out Java code! ./gradlew generateProto

Server implementation

To employ the server for our methods definition, first of all, we have to prolong the good abstract class, which had been generated in the previous step:

public class GeolocationServer extends GeolocationServerGrpc.GeolocationServerImplBase

As the following step insert the @GrpcService annotation at the class level to sign-up gRPC server and override server techniques:

public void insert(Geolocation request, StreamObserver responseObserver) 
    GeolocationEvent geolocationEvent = convertToGeolocationEvent(ask for)


general public void lookup(SearchRequest request, StreamObserver responseObserver) 
    List geolocationEvents = geolocationRepository.searchByVinAndOccurredOnFromTo(
        convertTimestampToInstant(ask for.getTo())

    Checklist geolocations =


  • StreamObserver<> responseObserver – stream of messages to deliver
  • responseObserver.onNext() – writes responses to the client. Unary calls should invoke onNext at most at the time
  • responseObserver.onCompleted() – gets a notification of thriving stream completion

We have to transform inside gRPC objects to our domain entities:

non-public GeolocationEvent convertToGeolocationEvent(Geolocation request) 
    Fast occurredOn = convertTimestampToInstant(request.getOccurredOn())
    return new GeolocationEvent(
        ask for.getSpeed().getValue(),
        new Coordinates(ask for.getCoordinates().getLatitude(), ask for.getCoordinates().getLongitude())

non-public Quick convertTimestampToInstant(Timestamp timestamp) 
    return Immediate.ofEpochSecond(timestamp.getSeconds(), timestamp.getNanos())

Error managing

Neither shopper normally sends us a valid information nor our process is resilient enough to take care of all errors, so we have to provide techniques to cope with exceptions.

If an error happens, gRPC returns a single of its mistake status codes rather, with an optional description.

We can handle it with ease in a Spring’s way, making use of annotations currently available in the library:

general public course GrpcExceptionAdvice 

    general public Position handleInvalidArgument(IllegalArgumentException e) 
        return Position.INVALID_ARGUMENT.withDescription(e.getMessage()).withCause(e)

  • @GrpcAdvice – marks the course as a container for particular exception handlers
  • @GrpcExceptionHandler – method to be invoked when an exception specified as an argument is thrown

Now we ensured that our error messages are clear and meaningful for clientele.

gRPC – is that the appropriate possibility for you?

As demonstrated in this short article, gRPC integrates properly with Spring Boot, so if you are familiar with it, the discovering curve is easy.

gRPC is a worthy option to look at when you are functioning with lower latency, highly scalable, distributed methods. It supplies an exact, efficient, and language-impartial protocol.

Look at out the formal documentation for more awareness! gRPC

Leave a Reply