dotnet-serialization

The best way to choose a .NET serialization format is to evaluate performance, versioning, and cross-platform needs. This decision framework maps your technical criteria to schema-based formats like Protobuf and MessagePack, or System.Text.Json with source generation for specific use cases.

To migrate from Newtonsoft.Json to System.Text.Json for AOT compatibility, evaluate source generators to eliminate reflection. This Skill provides a decision framework to apply this migration across APIs and microservices while validating compatibility and performance.

You need schema-based serialization like Protobuf or MessagePack when strict versioning and maximum performance outweigh human readability. This Skill identifies the technical criteria for selecting these formats over System.Text.Json for your messaging and persistence layers.

System.Text.Json works with Native AOT in .NET microservices by using source generators instead of reflection. This Skill evaluates source generation to ensure AOT compatibility and provides concrete recommendations for applying it in real-world service architectures.

Compare Protobuf, MessagePack, and System.Text.Json by validating performance and compatibility against a sample data contract. This Skill's quick start evaluation applies technical criteria to identify the optimal format for API design, balancing reflection-free AOT support with versioning requirements.