How to: Use the gRPC interface in your Dapr application

Mon, 01 Jan 0001 00:00:00 +0000

Dapr implements both an HTTP and a gRPC API for local calls. gRPC is useful for low-latency, high performance scenarios and has language integration using the proto clients.

Find a list of auto-generated clients in the Dapr SDK documentation.

The Dapr runtime implements a proto service that apps can communicate with via gRPC.

In addition to calling Dapr via gRPC, Dapr supports service-to-service calls with gRPC by acting as a proxy. Learn more in the gRPC service invocation how-to guide.

Serialization in Dapr's SDKs

Mon, 01 Jan 0001 00:00:00 +0000

Dapr SDKs provide serialization for two use cases. First, for API objects sent through request and response payloads. Second, for objects to be persisted. For both of these cases, a default serialization method is provided in each language SDK.

Language SDK	Default Serializer
.NET	DataContracts for remoted actors, System.Text.Json otherwise. Read more about .NET serialization here
Java	DefaultObjectSerializer for JSON serialization
JavaScript	JSON

Service invocation

 using var client = (new DaprClientBuilder()).Build();
 await client.InvokeMethodAsync("myappid", "saySomething", "My Message");

 DaprClient client = (new DaprClientBuilder()).build();
 client.invokeMethod("myappid", "saySomething", "My Message", HttpExtension.POST).block();

In the example above, the app myappid receives a POST request for the saySomething method with the request payload as "My Message" - quoted since the serializer will serialize the input String to JSON.

Local development on Dapr Docs

How to: Use the gRPC interface in your Dapr application

Serialization in Dapr's SDKs

Service invocation