...
Thin clients need a standardized way to serialize data for Table and Key-Value APIs. In 2.x, we used the same Ignite binary format that was used for server communication and data storage. However, in 3.x there are different formats for data storage and transmission (TODO: links), and those formats are not meant to be used by thin clients.
In Ignite 3.0 we want to avoid the cost of writing and supporting our own serialization mechanism.
The goal is to find an existing serialization format that satisfies the following requirements:
...