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:

Debugging with Chrome DevTools MCP: Giving AI eyes in the browser

Debugging with Chrome DevTools MCP: Giving AI eyes in the browser

Learn how to effectively debug with Chrome DevTools MCP server, which provides AI agents access to Chrome DevTools directly inside your favorite code editor.

Emmanuel John
Oct 21, 2025 ⋅ 6 min read
Goodbye, useState? Smarter state modeling for modern React apps

Goodbye, useState? Smarter state modeling for modern React apps

Ever opened a React file and found a graveyard of useState hooks? The problem isn’t React; it’s how we model state. Here’s how to do it smarter.

Oscar Jite-Orimiono
Oct 21, 2025 ⋅ 9 min read

Why third-party integrations break in React 19 — And how to future-proof them

React 19 breaks old third-party integrations. Learn why concurrent rendering exposes brittle SDKs and how to rebuild them with resilient modern patterns.

Peter Aideloje
Oct 20, 2025 ⋅ 4 min read
React useEffectEvent: Goodbye to stale closure headaches

React useEffectEvent: Goodbye to stale closure headaches

Discover why the useEffectEvent Hook is important, how to use it effectively, and how it compares to useRef.

David Omotayo
Oct 17, 2025 ⋅ 5 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

Hey there, want to help make our blog better?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now