fury-benchmarks VS grpc-dotnet

1) Fury is 41.6x faster than jackson for Struct serialization 2) Fury is 65.6x faster than jackson for Struct deserialization 3) Fury is 9.4x faster than jackson for MediaContent serialization 4) Fury is 9.6x faster than jackson for MediaContent deserialization

see https://github.com/chaokunyang/fury-benchmarks for detailed benchmark code.

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.