3 ms·
I'm looking to replace our current Boost.Serialization code with something else. I have the following requirements: - serialisation cannot be intrusive (i.e. I
by secondcoming 6y ago
I'm looking to replace our current Boost.Serialization code with something else. I have the following requirements:
- serialisation cannot be intrusive (i.e. I don't want a class definition to be generated from a schema file)
- zero copy
- some sort of versioning so any accidental message version mismatch between sender and receiver doesn't cause a crash / undefined behviour.
- many language support
Protobufs are intrusive, so that rules them out.
JSON is just too verbose and slow.
MessagePack looked like the most promising path to pursue at the moment. Flatbuffers look quite similar.
- awild 6y agoMy predecessor has employed smile in all our m2m communication. As far as I have understood it, it aims to be a binary representation of json. I cannot speak for its speed but I trust him to a certain extent.