Apache Ignite is a memory computing platform that is durable, consistent, and highly available, with powerful SQL, key-values, and processing APIs.
- Memory-Centric Storage
Apache Ignite is based on distributed memory-centric architecture that combines the performance and scale of in-memory computing together with the disk durability and strong consistency in one system.The main difference between the memory-centric approach and the traditional disk-centric approach is that the memory is treated as a fully functional storage, not just as a caching layer, like most databases do. For example, Apache Ignite can function in a pure in-memory mode, in which case it can be treated as an In-Memory Database (IMDB) and In-Memory Data Grid (IMDG) in one.
On the other hand, when persistence is turned on, Ignite begins to function as a memory-centric system where most of the processing happens in memory, but the data and indexes get persisted to disk. The main difference here from the traditional disk-centric RDBMS or NoSQL system is that Ignite is strongly consistent, horizontally scalable, and supports both SQL and key-value processing APIs.
Ignite provides full support for SQL, DDL and DML, allowing users to interact with Ignite using pure SQL without writing any code. This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes Ignite a one-of-a-kind distributed SQL database.
- Distributed Key-Value
The in-memory data grid component in Ignite is a fully transactional distributed key-value store that can scale horizontally across 100s of servers in the cluster. When persistence is enabled, Ignite can also store more data than fits in memory and survive full cluster restarts.
Apache Ignite 2.7.5 released.
- Added Java 11 support
- Fixed infinite looping during SSL handshake, affecting Java 11/Windows
- Fixed storage corruption case after incorrectly rotated page
- Erroneous WAL record after incorrectly rotated page processed automatically
- Addressed ignite.sh failure on Mac OS and Linux, affecting Java 11
- Launch scripts and some Ignite initialization steps were fixed for Java 12
- Fixed indexes corruption on node stop under load
- Fixed case of node crash during node deactivation
- Error message with advice about required JVM parameters printed when Java 9+ is used
- Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type