2020-08-28
2807
#rust
Andre Bogus
23972
Aug 28, 2020 â‹… 10 min read

Rust serialization: What’s ready for production today?

Andre Bogus Andre "llogiq" Bogus is a Rust contributor and Clippy maintainer. A musician-turned-programmer, he has worked in many fields, from voice acting and teaching, to programming and managing software projects. He enjoys learning new things and telling others about them.

Recent posts:

best JavaScript and HTML5 game engines

Best JavaScript and HTML5 game engines (updated for 2025)

Check out this guide, which ranks the top 10 JavaScript/HTML5 game engines by popularity, capability, and use case.

Solomon Eseme
May 2, 2025 â‹… 15 min read

React Compiler RC: What it means for React devs

The React team officially released the first Release Candidate (RC). Let’s go over what’s new in RC and what it means for React developers.

David Omotayo
May 2, 2025 â‹… 7 min read
Understanding Anthropic's Model Context Protocol (MCP)

Understanding Anthropic’s Model Context Protocol (MCP)

The Model Context Protocol (MCP) provides a standardized way for AI models to access contextual information from diverse data sources.

David Omotayo
May 2, 2025 â‹… 12 min read
Choosing The Best Access Control Model For Your Frontend

Choosing the best access control model for your frontend

Explore RBAC, ABAC, ACL, and PBAC access control methods and discover which one is ideal for your frontend use case.

Temitope Oyedele
May 1, 2025 â‹… 10 min read
View all posts

4 Replies to "Rust serialization: What’s ready for production today?"

  1. Hi Ander,

    Thanks for the interesting article.
    I try to understand the background of the serialization/deserialization methods on the Serde. For example, how the BinCode serialization method encodes data and which metadata store after encoding.

    Best,
    Saeed

  2. This is great. I really appreciate this concise overview which is exactly what I needed to start shopping. One thing though that would help immensely is if, at least in the comparison table, the units were all standard or if there was an option to make them standard or to sort them. For today, I will calculate them in a spreadsheet (happy to share, obviously) but I’m sure the next person who wants to use this the same way will appreciate the lack of an extra step.

    Thanks for all the great work!

    1. Thanks for the nice words. The units *are* all standard SI units. But I think you may actually mean they should be the same unit (e.g. nanoseconds). The downside is that this would yield some pretty big numbers which aren’t that easy to parse either. I’ll try and see if a nanosecond-based comparison is any easier to read.

  3. MessagePack is a self describing protocol and therefore has to encode the field names (‘variant’,’opt_bool’,’vec_strs’,’range’). I really can’t see how this would fit into 24 bytes total, only the field names would take 28 bytes (so without any protocol overhead and values) if I’m counting correctly…

Leave a Reply