Ignite for NoSQL Users

Apache Ignite as many other NoSQL databases is horizontally scalable, highly available and fault-tolerant. Ignite acts as a distributed partitioned hash map making sure that every cluster node owns a portion of the overall data set. This way the more cluster nodes you add, the more data you can store in the cluster.

Ignite can either partition or replicate the data. Unlike REPLICATED mode, where data is fully replicated across all nodes in the cluster, in PARTITIONED mode Ignite will equally split the data across multiple cluster nodes, allowing for storing TBs of data both in memory and on disk.

FeatureNoSQLIgnite
Scalability horizontal horizontal
Availability high high
Consistency eventual strong
In-Memory in-memory store
Persistence
SQL
Key-Value
Collocated Processing
Scalability
NoSQL horizontal
Ignite horizontal
Availability
NoSQL high
Ignite high
Consistency
NoSQL eventual
Ignite strong
In-Memory
NoSQL
Ignite in-memory store
Persistence
NoSQL
Ignite
SQL
NoSQL
Ignite
Key-Value
NoSQL
Ignite
Collocated-Processing
NoSQL
Ignite

Unlike eventually consistent NoSQL databases, Ignite can operate in a strongly consistent mode, guaranteeing the data consistency across all cluster nodes. Ignite is a fully ACID-compliant platform.

The other difference between Ignite and NoSQL databases is that, first, the memory is treated as a fully functional storage, not just as a caching layer, like most databases do. Second, in addition to key-value APIs, Ignite supports distributed SQL and collocated processing approach.