Utf8Json VS Protobuf.NET

This looks like a fun project but for serious work, if you need runtime codegen, you should use .NET which has been successfully using reflection and IL emit for more than a decade:

- Regex https://github.com/dotnet/runtime/blob/main/src/libraries/Sy...

- Json https://github.com/neuecc/Utf8Json/tree/master?tab=readme-ov... (this project is archived but nonetheless impressive and continues to show good numbers despite obsoletion)

- LINQ to DB query compilation https://github.com/dotnet/efcore/blob/main/src/EFCore/Query/...

While I posted a solution that would do this, I'd call this premature optimization. The only time I'd even consider doing this is in a hot path. Here's a good reason to focus on branchless programming: https://github.com/neuecc/Utf8Json.

Now try Utf8Json.

If my game state was smaller I would go for https://github.com/neuecc/Utf8Json and serde_json combination. Would save me some time with rmp_serde customization.

protobuf-net is a contract based serializer for .NET code, that happens to write data in the "protocol buffers" serialization format engineered by Google.

To get started, download the Protobuf-net NuGet package from NuGet.

This article requires that reader is familar with core concept of Akka.NET serialization (see https://getakka.net/articles/serialization/serialization.html) and ProtoBuf-Net library (see https://github.com/protobuf-net/protobuf-net).

The model used, a simple invoice which uses protobuf-net 1 NuGet package to store information in a binary file.

Not sure if it works with gRPC but I really like how Protobuf.NET uses attributes like other serializers instead of needing to write a .proto and generate (not-very-C#-friendly) classes from it. Well, until you need to interop with other languages.

I mentioned JSON, but there are many formats that are much more efficient. I can mention FlatBuffers, MessagePack and ProtoBuf. These are the ones I've used myself, and personally I'm most comfortable with MessagePack and ProtoBuf. I don't think the performance would be an issue if you had to choose between these three, it's mostly the API that is different.

The closest way would be using Grpc.Web + Protobuf.net. The overall experience is pretty close to WCF server + Client where you share a common interface and let the client and server just call through those.

Grpc Web with Blazor WASM is a really pleasant experience so far imo for my personal projects at home. You have strongly typed models and methods and you have choice on sharing the contract between client and server if you're using code first instead of proto IDL files (e.g. protobuf-net).

It's pretty straight-forward to follow the protobuf-net docs to serialize the report, but we should really GZIP the stream for sending to reduce bandwidth consumption and improve performance: