Ignite comes with a powerful a Key-Value Store (a.k.a. Key-Value Database). It can be viewed as a distributed partitioned hash map with every cluster node owning a portion of the overall data set.
Ignite key-value store complies with JCache (JSR 107) specification and provides distributed ACID transactions, scan and continuous queries, collocated processing and more.
Depending on the configuration, Ignite can either partition or replicate data.
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.
Ignite also allows to configure multiple backup copies to guarantee data resiliency in case of failures.
Regardless of which replication scheme is used, Ignite guarantees data consistency across all cluster members.
Data can be stored both in RAM and, optionally, on disk if Ignite Native Persistence is enabled.
Ignite also can automatically utilize 3rd party databases as storage, including integration with most RDBMS, NoSQL or Hadoop systems.
Unlike other key-value databases, Ignite determines data locality using a pluggable hashing algorithm. Every client can determine which node a key belongs to by plugging it into a hashing function, without a need for any special mapping servers or name nodes.
Check Data Grid for more information.