...

• MsgPack as underlying binary format (IEP-75 Thin Client MsgPack Serialization)
• Different set of data types (IEP-54: Schema-first Approach)
• More flexible and extensible handshake with magic header string

TCP Socket

• Every Ignite node listens on a TCP port. Thin client implementations connect to any node in the cluster (possibly multiple nodes) through a TCP socket and perform Ignite operations using a well-defined binary protocol.
• Server-side connection parameters are defined in ClientConnectorConfiguration class.
  • Default port is 10800.
  • Connector is enabled by default, no configuration changes needed.
• Netty is used on the server for network IO.

Data Format

MsgPack is used for data serialization.

Custom Data Types

In addition to built-in MsgPack types, the following types are defined:

Handshake

TODO: Magic word, features as map 

Risks and Assumptions

TODO

...