...

Dynamic Type Registration, Serializable Types

BinaryConfiguration is  is no longer required - , any type can be used in Cache and Compute right away. All objects are written in Ignite binary format (which means IBinary and SQL APIs always work).Serializable types (including those which implement ISerializable) are also written using Ignite binary format. Learn more from this documentation: https://apacheignite-net.readme.io/docs/serialization, including types implementing interface. See documentation for more information [8].

Binary Name Mapping

Ignite.NET 1.9 and earlier uses simple name mapping only, which means Object.GetType().Name is used to map type name to type id. Ignite.NET 2.0 uses full name mapping by default, which includes namespace, generics and array dimensions. This change may affect multi-platform Ignite applications where Java and .NET types are mapped to each other. More details: https://apacheignite-net.readme.io/docs/platform-interoperabilitySee documentation for more information [9].

TODO

Cache plugins - ?

CPP - ?

...

[7] https://apacheignite-tools.readme.io/docs/automatic-rdbms-integration

[8] https://apacheignite-net.readme.io/docs/serialization

[9] https://apacheignite-net.readme.io/docs/platform-interoperability