...

1. There is no true random access to fields by name in MsgPack - offsets are not stored, values are written sequentially. Though it is possible to skip values without reading them.
2. Some types, like UUID and date/time, will require custom handling (e.g. UUID is written as string by default, which is not optimal). MsgPack allows up to 128 custom types to be defined.
3. To be able to read user objects separately and efficiently without deserializing them (e.g. key and value in put operation), we'll have to wrap them one of the following ways:
   1. As a byte array (MsgPack bin format) - "MsgPack within MsgPack".
   2. Custom MsgPack type with size in the header

Discussion Links

...

• http://apache-ignite-developers.2346864.n4.nabble.com/IEP-75-Thin-Client-MsgPack-Serialization-for-3-0-td52854.html

Reference Links

• MsgPack spec https://github.com/msgpack/msgpack/blob/master/spec.md
• Benchmarks Ignite vs MsgPack https://github.com/apache/ignite/pull/9178
• https://en.wikipedia.org/wiki/Comparison_of_data-serialization_formats
  • Google sheet with filters: https://docs.google.com/spreadsheets/d/12fnJG3rLlsVAivOA93K-6eSC8duM3oNLG39wNCNcjCc/edit?usp=sharing
• https://stackoverflow.com/questions/6355497/performant-entity-serialization-bson-vs-messagepack-vs-json
• https://serde.rs/
• MessagePack vs CBOR
• Hackernews: MessagePack vs CBOR (https://news.ycombinator.com/item?id=14067747)
• https://aloiskraus.wordpress.com/2019/09/29/net-serialization-benchmark-2019-roundup/

...