...

Apache Ignite 2.0 is based on the new page memory architecture. Data is always stored offheap, with ability to optionally cache small portion in Java heap. Please refer to documentation to learn more about new concepts and configuration parameters See documentation for more information [1]. 

Configuration

IgniteConfiguration

...

Previously existed eviction mechanisms based on EvictionPolicy is now supported only for optional near and Java heap caching of the data stored in the offheap page memory. To enable the eviction for the page memory, use DataPageEvictionMode enumeration. See documentation for more details [2] for more details.

CollectionConfiguration

• memoryMode property has been removed due to new Ignite page memory architecture [1]

...

IgniteAsyncSupport interface is now deprecated and will be removed in future Apache Ignite releases. Use methods with Async suffix instead. See documentation for more information [4] for more information.

Old style:

IgniteCache<K, V> asyncCache = cache.withAsync();
 
asyncCache.getAsync(key);
 
IgniteFuture<V> future = asyncCache.future();

...

Apache Ignite 2.0 integrates with Hibernate 5.0. The previous integration with a legacy Hibernate version of 4.2 can be used by importing ignite-hibernate_4.2 maven artifact or taking a respective JAR file from distribution. See documentation for more details [65]

Redis

Default Redis cache name was changed from null to  default. See documentation for more details [56]

Ignite.NET

CompiledQuery2

...

[4] https://apacheignite.readme.io/docs/async-support

[5] https://apacheignite-mix.readme.io/docs/redishibernate-l2-cache

[6] https://apacheignite-mix.readme.io/docs/hibernate-l2-cacheredis

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

...