| <!-- |
| ▄▄▄ ██▓███ ▄▄▄ ▄████▄ ██░ ██ ▓█████ ██▓ ▄████ ███▄ █ ██▓▄▄▄█████▓▓█████ |
| ▒████▄ ▓██░ ██▒▒████▄ ▒██▀ ▀█ ▓██░ ██▒▓█ ▀ ▓██▒ ██▒ ▀█▒ ██ ▀█ █ ▓██▒▓ ██▒ ▓▒▓█ ▀ |
| ▒██ ▀█▄ ▓██░ ██▓▒▒██ ▀█▄ ▒▓█ ▄ ▒██▀▀██░▒███ ▒██▒▒██░▄▄▄░▓██ ▀█ ██▒▒██▒▒ ▓██░ ▒░▒███ |
| ░██▄▄▄▄██ ▒██▄█▓▒ ▒░██▄▄▄▄██ ▒▓▓▄ ▄██▒░▓█ ░██ ▒▓█ ▄ ░██░░▓█ ██▓▓██▒ ▐▌██▒░██░░ ▓██▓ ░ ▒▓█ ▄ |
| ▓█ ▓██▒▒██▒ ░ ░ ▓█ ▓██▒▒ ▓███▀ ░░▓█▒░██▓░▒████▒ ░██░░▒▓███▀▒▒██░ ▓██░░██░ ▒██▒ ░ ░▒████▒ |
| ▒▒ ▓▒█░▒▓▒░ ░ ░ ▒▒ ▓▒█░░ ░▒ ▒ ░ ▒ ░░▒░▒░░ ▒░ ░ ░▓ ░▒ ▒ ░ ▒░ ▒ ▒ ░▓ ▒ ░░ ░░ ▒░ ░ |
| ▒ ▒▒ ░░▒ ░ ▒ ▒▒ ░ ░ ▒ ▒ ░▒░ ░ ░ ░ ░ ▒ ░ ░ ░ ░ ░░ ░ ▒░ ▒ ░ ░ ░ ░ ░ |
| ░ ▒ ░░ ░ ▒ ░ ░ ░░ ░ ░ ▒ ░░ ░ ░ ░ ░ ░ ▒ ░ ░ ░ |
| ░ ░ ░ ░░ ░ ░ ░ ░ ░ ░ ░ ░ ░ ░ ░ ░ |
| --> |
| |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one |
| or more contributor license agreements. See the NOTICE file |
| distributed with this work for additional information |
| regarding copyright ownership. The ASF licenses this file |
| to you under the Apache License, Version 2.0 (the |
| "License"); you may not use this file except in compliance |
| with the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, |
| software distributed under the License is distributed on an |
| "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
| "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
| KIND, either express or implied. See the License for the |
| specific language governing permissions and limitations |
| under the License. |
| --> |
| |
| <!DOCTYPE html> |
| <html> |
| <head> |
| <link rel="canonical" href="https://ignite.apache.org/use-cases/database/key-value-store.html"/> |
| <meta charset="utf-8"> |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| <title>Key-Value Store - Apache Ignite</title> |
| <link media="all" rel="stylesheet" href="/css/all.css?v=1514336028"> |
| <link href="https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css" rel="stylesheet"> |
| <link media="all" rel="stylesheet" href="/css/syntaxhighlighter.css"> |
| <link href='https://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,600italic,700,700italic,800,800italic' |
| rel='stylesheet' type='text/css'> |
| |
| <!--#include virtual="/includes/sh.html" --> |
| </head> |
| <body> |
| <div id="wrapper"> |
| <!--#include virtual="/includes/header.html" --> |
| |
| <main id="main" role="main" class="container"> |
| <section id="key-value-store" class="page-section"> |
| <h1 class="first">Key-Value Store</h1> |
| <div class="col-sm-12 col-md-12 col-xs-12" style="padding:0 0 10px 0;"> |
| <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0"> |
| <p> |
| Ignite can be accessed with simple key-value APIs and, thus, act as a distributed key-value store |
| (aka. <a href="/features/datagrid.html">data grid</a>). In this scenario, you can think of Ignite as of a distributed partitioned |
| hash map with every cluster node owning a portion of the overall data set. It's worth mentioning, |
| that even if you see or use Ignite as a key-value store, you're not limited to the key-value operations |
| and can always leverage from other available APIs such as SQL, collocated computations, machine |
| learning, streaming. |
| </p> |
| </div> |
| <div class="col-sm-6 col-md- col-xs-12" style="padding-right:0"> |
| <img class="img-responsive" src="/images/data_grid.png" width="500px" style="float:right;"/> |
| </div> |
| </div> |
| |
| <div class="page-heading">JCache APIs</div> |
| <p> |
| Ignite key-value APIs comply with <a href="/use-cases/caching/jcache-provider.html">JCache (JSR 107)</a> |
| specification that supports the following: |
| </p> |
| <ul class="page-list"> |
| <li>In-Memory Key Value Store</li> |
| <li>Basic Cache Operations</li> |
| <li>ConcurrentMap APIs</li> |
| <li>Collocated Processing (EntryProcessor)</li> |
| <li>Events and Metrics</li> |
| <li>Pluggable Persistence</li> |
| </ul> |
| |
| <div class="page-heading">Extended Key-Value APIs</div> |
| <p> |
| In addition to the standard JCache API, Ignites supports distributed ACID transactions, |
| scan and continuous queries, collocated processing and more. |
| </p> |
| |
| <div class="code-examples"> |
| <div class="page-heading">Code Examples</div> |
| <!-- Nav tabs --> |
| <ul id="datagrid-examples" class="nav nav-tabs"> |
| <li class="active"><a href="#datagrid-example-basic" role="tab" data-toggle="tab">Put and Get</a></li> |
| <li><a href="#datagrid-example-transactions" role="tab" data-toggle="tab">Transactions</a></li> |
| <li><a href="#datagrid-example-locks" role="tab" data-toggle="tab">Locks</a></li> |
| </ul> |
| |
| <!-- Tab panes --> |
| <div class="tab-content"> |
| <div role="tabpanel" class="tab-pane active" id="datagrid-example-basic"> |
| <pre class="brush:java"> |
| Ignite ignite = Ignition.ignite(); |
| |
| // Get an instance of named cache. |
| final IgniteCache<Integer, String> cache = ignite.cache("cacheName"); |
| |
| // Store keys in cache. |
| for (int i = 0; i < 10; i++) |
| cache.put(i, Integer.toString(i)); |
| |
| // Retrieve values from cache. |
| for (int i = 0; i < 10; i++) |
| System.out.println("Got [key=" + i + ", val=" + cache.get(i) + ']'); |
| |
| // Remove objects from cache. |
| for (int i = 0; i < 10; i++) |
| cache.remove(i); |
| |
| // Atomic put-if-absent. |
| cache.putIfAbsent(1, "1"); |
| |
| // Atomic replace. |
| cache.replace(1, "1", "2"); |
| </pre> |
| </div> |
| <div role="tabpanel" class="tab-pane" id="datagrid-example-transactions"> |
| <pre class="brush:java"> |
| Ignite ignite = Ignition.ignite(); |
| |
| // Clone every object we get from cache, so we can freely update it. |
| IgniteCache<Integer, Account> cache = ignite.cache("cacheName"); |
| |
| try (IgniteTx tx = Ignition.ignite().transactions().txStart()) { |
| Account acct = cache.get(acctId); |
| |
| assert acct != null; |
| |
| // Deposit $20 into account. |
| acct.setBalance(acct.getBalance() + 20); |
| |
| // Store updated account in cache. |
| cache.put(acctId, acct); |
| |
| tx.commit(); |
| } |
| </pre> |
| </div> |
| <div role="tabpanel" class="tab-pane" id="datagrid-example-locks"> |
| <pre class="brush:java"> |
| Ignite ignite = Ignition.ignite(); |
| |
| // Get an instance of named cache. |
| final GridCache<String, Integer> cache = ignite.cache("cacheName"); |
| |
| // Lock cache key "Hello". |
| Lock lock = cache.lock("Hello"); |
| |
| lock.lock(); |
| |
| try { |
| cache.put("Hello", 11); |
| cache.put("World", 22); |
| } |
| finally { |
| lock.unlock(); |
| } |
| </pre> |
| </div> |
| </div> |
| </div> |
| |
| <section id="key-features" class="page-section"> |
| <h2>More on Key-Value APIs</h2> |
| <table class="formatted" name="key-value-apis"> |
| <thead> |
| <tr> |
| <th width="35%" class="left">Feature</th> |
| <th>Description</th> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td class="left">Data Grid</td> |
| <td> |
| <p> |
| Ignite data grid is a <code>key-value store</code> which can store data both, in-memory |
| and on-disk. It can be viewed as a distributed partitioned hash map, with every cluster |
| node owning a portion of the overall data. This way the more cluster nodes we add, |
| the more data we can store: |
| </p> |
| |
| <div class="page-links"> |
| <a href="/features/datagrid.html">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Durable Memory</td> |
| <td> |
| <p> |
| Ignite <code>Durable Memory</code> allows storing and processing data and indexes |
| both, in memory and on disk. The in-memory data, including indexes, is always |
| stored and managed <code>off-heap</code>, completely removing any type of Garbage |
| Collection overhead. |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/durable-memory" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">JCache (JSR 107)</td> |
| <td> |
| <p> |
| Ignite is a 100% compliant implementation of <span style="white-space: nowrap">JCache (JSR 107)</span> specification. |
| JCache provides a very simple to use, yet very powerful API for data caching: |
| </p> |
| <div class="page-links"> |
| <a href="/use-cases/caching/jcache-provider.html">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Memory-Centric Storage</td> |
| <td> |
| <p> |
| Apache Ignite is based on distributed <i>memory-centric architecture</i> that combines the |
| performance and scale of in-memory computing together with the disk durability and strong |
| consistency in one system: |
| </p> |
| <div class="page-links"> |
| <a href="/arch/memorycentric.html">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Collocated Processing</td> |
| <td> |
| <p> |
| Ignite allows executing any native Java, C++, and .NET/C# code directly on the server-side, |
| close to the data, in collocated fashion: |
| </p> |
| <div class="page-links"> |
| <a href="/features/collocatedprocessing.html" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Client-side Near Caches</td> |
| <td> |
| <p> |
| Near cache is local client-side cache that stores the most recently and most frequently accessed data. |
| </p> |
| <div class="page-links"> |
| <a href="http://apacheignite.readme.io/docs/near-caches" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">ACID Transactions</td> |
| <td> |
| <p> |
| Ignite provides fully ACID compliant distributed transactions that ensure guaranteed consistency. |
| </p> |
| <div class="page-links"> |
| <a href="/features/transactions.html">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left" width="35%">Deadlock-Free Transactions</td> |
| <td> |
| <p> |
| Ignite supports deadlock-free, optimistic transactions, which do not acquire any locks, |
| and free users from worrying about the lock order. |
| Such transactions also provide much better performance: |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/transactions" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left" width="35%">Transactional Entry Processor</td> |
| <td> |
| <p> |
| Ignite transactional entry processor allows executing collocated user logic on the server |
| side within a transaction: |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/affinity-collocation#ignitecompute-vs-entryprocessor" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left" width="35%">Cross-Partition Transactions</td> |
| <td> |
| <p> |
| In Ignite, transactions can be performed on all partitions of a cache across the whole |
| cluster: |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/transactions#ignitetransactions" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left" width="35%">Locks</td> |
| <td> |
| <p> |
| Ignite allows developers to define explicit locks enforcing mutual exclusion on cached objects: |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/distributed-locks" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left" width="35%">Continuous Queries</td> |
| <td> |
| <p> |
| Continuous queries are useful for cases when you want to execute a query and then |
| continue to get notified about the data changes that fall into your query filter: |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/continuous-queries" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left" width="35%">Write-Through</td> |
| <td> |
| <p> |
| Write-Through mode allows updating the data in the database. |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/3rd-party-store#read-through-and-write-through" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Read-Through</td> |
| <td> |
| <p> |
| Read-Through mode allows reading the data from the database. |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/3rd-party-store#read-through-and-write-through" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Write-Behind Caching</td> |
| <td> |
| <p> |
| Ignite provides an option to asynchronously perform updates to the database via Write-Behind Caching. |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite.readme.io/docs/3rd-party-store#section-write-behind-caching" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Hibernate L2 Caching</td> |
| <td> |
| <p> |
| Ignite data grid can be used as <code>Hibernate Second-Level Cache</code> (or L2 cache), |
| which can significantly speed-up the persistence layer of your application. |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite-mix.readme.io/docs/hibernate-l2-cache" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Spring Caching</td> |
| <td> |
| <p> |
| Ignite provides Spring-annotation-based way to enable caching for Java methods so that |
| the result of a method execution is stored in the Ignite cache. If later the same |
| method is called with the same set of parameters, the result will be retrieved from |
| the cache instead of actually executing the method. |
| </p> |
| <div class="page-links"> |
| <a href="http://apacheignite-mix.readme.io/docs/spring-caching" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">Spring Data</td> |
| <td> |
| <p> |
| Apache Ignite implements Spring Data <code>CrudRepository</code> interface that not only supports basic CRUD operations but also provides access to the Apache Ignite SQL capabilities via the unified Spring Data API. |
| </p> |
| <div class="page-links"> |
| <a href="https://apacheignite-mix.readme.io/docs/spring-data" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| <tr> |
| <td class="left">OSGI Support</td> |
| <td> |
| <p></p> |
| <div class="page-links"> |
| <a href="https://apacheignite-mix.readme.io/docs/starting-inside-an-osgi-container" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a> |
| </div> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </section> |
| </section> |
| </main> |
| |
| <!--#include virtual="/includes/footer.html" --> |
| </div> |
| <!--#include virtual="/includes/scripts.html" --> |
| </body> |
| </html> |
