4 ms·

There is some strange geeky enjoyment from browsing all the serialization libraries out there. For my taste, I have centered on Cereal. When workind with C++

There is some strange geeky enjoyment from browsing all the serialization libraries out there. For my taste, I have centered on Cereal. When workind with C++ end to end, I have found it to be the easiest and fastest way to throw data around.

Heliosmaster 9y ago
Serialization can easily be a bottleneck, especially for write-heavy systems (like we do, with Event Sourcing). So i think it's quite natural that people try and squeeze the last few milliseconds out of it. It can easily make a huge difference when serializing/deserializing billions of entities
- fh973 9y ago
  Serialization is order of microseconds, not milliseconds.
  - kbenson 9y ago
    That depends entirely on how much (in both quantity and size) you are serializing, doesn't it?
  - kentonv 9y ago
    I've seen single messages that took milliseconds... or even seconds.
- spullara 9y ago
  Microservice architecture CPU usage can be dominated by serialization. It is one of the reasons that the JVM was so much faster than Ruby at Twitter for the frontend. The business logic just didn't matter as much as deserializing thrift and serializing json or html.
pagnol 9y ago
There's a Wikipedia article that provides a nice overview: https://en.wikipedia.org/wiki/Comparison_of_data_serialization_formats https://en.wikipedia.org/wiki/Comparison_of_data_serializati...