grpc-dotnet VS grpcurl

Official gRPC Repository on GitHub

Given it's a binary serialization framework, it should not be too difficult, because the domain is well-explored and numerous libraries exist in C# which address same goals that Fury does.

More popular/newer examples are https://github.com/Cysharp/MemoryPack (which is similar to Fury with its own spec, C#-code first schema), https://github.com/MessagePack-CSharp/MessagePack-CSharp or even gRPC / Protobuf tooling https://github.com/grpc/grpc-dotnet

And I used Unity because I wanted a tool/engine that I can use to build the game for multiple platforms at once, however, after a while I realized that the game is really simple and I'm not utilizing Unity. Actually, it was quite the opposite, the performance of the game (when it comes to simple animations like drag and drop) was not that good, the size was large, and some tools like gRPC-net are not maintained anymore for Unity.

You can refer to this grpc spa example. It also demonstrates how to use grpc instead of restful API to communicate with dotnet backends.

grpcurl

The API server will be built and start running on port 50051. You can test the functionality using a gRPC client of your choice like grpcurl or Postman.

> What is the ubiquitous utility for interacting with gRPC? We have curl for REST. What is openAPI of gRPC?

grpcurl[1] combined with gRPC server reflection[2]. The schema is compiled into the server as an encoded proto which is exposed via server reflection, which grpcurl reads to send correctly encoded requests.

[1] https://github.com/fullstorydev/grpcurl

The whole idea behind the post is that accessing the gRPC service with regular tools is impossible. To test, we need a dedicated tool nonetheless. I found grpcurl. Let's install it and use it to list available services:

gRpcurl is a cool little tool to look at btw. Had to use it at my job before. Can call a gRPC via a curl like command. Regular curl doesn't support HTTP2. Had to use TLS with some tokens even. But you can reference a local .proto(gRPC protobuf file for the call) and make things easier for yourself if you hate reading instructions on command line args like I do.

A simple GRPC client built using grpcurl.

Try testing with grpcurl, using the -H or -rpc-header flags to set the appropriate header.