gRPC services in GeneXus

gRPC services are implemented in GeneXus through the API object. 

Unlike the REST API, the gRPC API provides greater security and performance, making it ideal for scenarios that require repeatedly sending large volumes of data.  

Another case where gRPC can be used is when gRPC is already available in the service and you want to add another service. In that case, due to compatibility reasons or corporate policy, the service should be gRPC. 

For more use cases, go to gRPC services. 

The implementation process of gRPC services in GeneXus is described in detail in Implementation of gRPC services through the API object, but you should keep in mind the following restrictions:

1. Despite the identical syntax, the RestPath and RestMethod annotations do not apply to gRPC.
2. The service has a single name in gRPC. 
3. The call to gRPC services requires native programs declared in GeneXus as external objects.
4. REST API and gRPC API have independent implementations. 

Availability

• This functionality is available as Beta since GeneXus 18 Upgrade 1.
• Since GeneXus 18 Upgrade 13, gRPC services are secured with the same specifications and mechanisms as secure REST services, operating behind the GAM security layer. Read more at HowTo: Set Up a Secure gRPC API Object using GAM and Remote Modules.