4 ms·

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 an

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.