Distributed Database For
High‑Performance Applications
With In‑Memory Speed

Scale Across Memory And Disk Without Compromise

Use Ignite Core Capabilities To Start Easily
And Scale Faster

Multi-Tier Storage

Ignite scales up and out across memory and disk. By default, Ignite operates in a pure in-memory mode. But, by toggling a single configuration setting, you can turn a cluster into a database that can grow beyond the cluster's memory capacity:

 <bean class="org.apache.ignite.configuration.IgniteConfiguration">
    <property name="dataStorageConfiguration">
        <bean class="org.apache.ignite.configuration.DataStorageConfiguration">
            <property name="defaultDataRegionConfiguration">
                <bean class="org.apache.ignite.configuration.DataRegionConfiguration">
                    <property name="persistenceEnabled" value="true"/>
 IgniteConfiguration cfg = new IgniteConfiguration();

DataStorageConfiguration storageCfg = new DataStorageConfiguration();

// Enable Ignite Persistence

// Using the new storage configuration
 var cfg = new IgniteConfiguration
    DataStorageConfiguration = new DataStorageConfiguration
        DefaultDataRegionConfiguration = new DataRegionConfiguration
            Name = "Default_Region",
            PersistenceEnabled = true

Distributed SQL

Use Ignite as a traditional SQL database by leveraging JDBC drivers, ODBC drivers, or the native SQL APIs that are available for Java, C#, C++, Python, and other programming languages. Seamlessly join, group, aggregate, and order your distributed in-memory and on-disk data:

 SELECT country.name, city.name, MAX(city.population) as max_pop
FROM country JOIN city ON city.countrycode = country.code
WHERE country.code IN ('USA','BRA','ESP','JPN')
GROUP BY country.name, city.name

ACID Transactions

Ignite can operate in a strongly consistent mode that provides full support for distributed ACID transactions. Transact across multiple cluster nodes, caches, tables, and partitions:

 IgniteTransactions transactions = ignite.transactions();

try (Transaction tx = transactions.txStart()) {
    Integer hello = cache.get("Hello");

    if (hello == 1)
        cache.put("Hello", 11);

    cache.put("World", 22);

 var transactions = ignite.GetTransactions();

using (var tx = transactions.TxStart()) {
    int hello = cache.Get("Hello");

    if (hello == 1) {
        cache.Put("Hello", 11);

    cache.Put("World", 22);


Compute APIs In Java, Scala, Kotlin, C#, C++

With traditional databases, for in-place calculations, you use stored procedures that are written in a language such as PL/SQL. With Ignite, you use modern JVM languages, C# or C++ to develop and execute custom tasks across your distributed database:

 // Broadcast the task to server nodes only.
IgniteCompute compute = ignite.compute(ignite.cluster().forServers());

// Each remote server node will execute the logic of the task/lambda below.
compute.broadcast(() -> System.out.println(
    "Hello Node: " + ignite.cluster().localNode().id()));
 // Broadcast the task to server nodes only.
var compute = ignite.GetCluster().ForServers().GetCompute();

// Each remote server node will execute the custom PrintNodeIdAction task.
compute.Broadcast(new PrintNodeIdAction());

Built-In Machine Learning

Ignite machine learning uses built-in algorithms and tools, as well as TensorFlow integration, to enable the building of scalable machine learning models and avoid costly data transfers. Train, deploy, evaluate, and update your ML and DL models continuously and at scale:

 // Create the trainer
KNNClassificationTrainer trainer = new KNNClassificationTrainer()
.withDistanceMeasure(new EuclideanDistance())

// Train the model
KNNClassificationModel knnMdl = trainer.fit(ignite, dataCache, vectorizer);

// Make a prediction
double prediction = knnMdl.predict(observation);

Continuous Queries

With relational databases, you use triggers to react to certain events. With Ignite, you deploy continuous queries that are written in a modern programming language such as Java or C# and process streams of changes on the database and application side:

 ContinuousQuery qry = new ContinuousQuery<>();

// The callback that will be triggered on the application side.
qry.setLocalListener(new MyLocalListener());

// The callback that will be executed on the server side.
qry.setRemoteFilterFactory(new MyRemoteFilterFactory());

// Deploy the query in the cluster.
 var cache = ignite.GetOrCreateCache("myCache");

var query = new ContinuousQuery(
    new MyLocalListener(), // Will be triggered on the application side.
    new MyRemoteFilter()); // Will be executed on the server side.

// Deploy the query in the cluster.
var handle = cache.QueryContinuous(query);

New To Ignite?
Three Primary Usage Scenarios

Application Acceleration
& Scale Out

Accelerate your existing applications by 100x using Ignite as an in-memory cache or in-memory data grid that is deployed over one or more external databases.

Distributed Database For
HTAP Workloads

Build applications that support transactional and analytical workloads by using Ignite as a database that scales beyond available memory capacity.

Digital Integration Hub

Create an advanced platform architecture that aggregates multiple back-end systems and databases into a low-latency and shared data store.

Ignite User Stories

Watch Other Stories

Join The Community At Events
And Meetups Worldwide

Ignite Virtual Meetup

Experts and practitioners give online talks and presentations and share their Apache Ignite experience.



Ignite Summit

This virtual conference is a chance to learn more about up-to-date in-memory computing solutions.

There are speakers from industry-leading companies and hundreds of participants from all over the world.



Other Events

Join us for conferences, presentations, and webinars to learn more about in-memory computing technologies.


View All Events

Resources To Elevate Your
Ignite Experience

Get access to a variety of free technical
and learning resources
View All Resources

Ready To Start?

Discover our quick start guides and build your first
application in 5-10 minutes