You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by ds...@apache.org on 2017/09/16 01:44:57 UTC
svn commit: r1808492 -
/ignite/site/trunk/use-cases/database/in-memory-database.html
Author: dsetrakyan
Date: Sat Sep 16 01:44:57 2017
New Revision: 1808492
URL: http://svn.apache.org/viewvc?rev=1808492&view=rev
Log:
minor.
Modified:
ignite/site/trunk/use-cases/database/in-memory-database.html
Modified: ignite/site/trunk/use-cases/database/in-memory-database.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/in-memory-database.html?rev=1808492&r1=1808491&r2=1808492&view=diff
==============================================================================
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Sat Sep 16 01:44:57 2017
@@ -54,21 +54,28 @@ under the License.
<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>
- Apache Ignite can be used as all-in-one <a href="/use-cases/database/distributed-database.html">
- distributed database</a> that supports SQL, key-value, compute, machine learning and other
- data processing APIs.
+ Apache Ignite can be used as a distributed and horizontally scalable
+ <code>in-memory database</code> (IMDB) that supports ACID transactions and
+ can be used with SQL, key-value, compute, machine learning and other data processing APIs.
</p>
<p>
- With Ignite <a href="/features/durablememory.html">Durable Memory</a>
- architecture, data as well as indexes can be stored both in memory and, optionally, on disk.
- This allows executing distributed SQL, key-value and other operations across different memory
- layers achieving the performance and scale of in-memory computing together with the disk
- durability and strong consistency in one system.
+ With Ignite <a href="/features/durablememory.html">durable memory</a>
+ architecture, data and indexes can be stored both, in memory and on disk. The disk persistence
+ is optional. When persistence is turned on, Ignite can store more data than fits in the available memory, and
+ will act as a complete <a href="/use-cases/database/distributed-database.html">distributed SQL database</a>.
</p>
<p>
- In the scenarios, when the whole data set and indexes fit in memory and the persistence is disabled
- on purpose, Apache Ignite will function as a full-fledged <i>in-memory database</i> supporting
- all the existing APIs for a pure in-memory use case.
+ In scenarios when the whole data set and indexes fit in memory, and the persistence is disabled,
+ Ignite will function as a pure <code>in-memory database</code> supporting SQL, together with
+ all the existing APIs for pure in-memory use cases.
+ </p>
+ <p>
+ One of distinguishing characteristics of Ignite SQL is the support for
+ <a href="https://apacheignite.readme.io/docs/sql-queries#distributed-joins" target="_blank">distributed SQL JOINs</a>,
+ which work in both, collocated and non-collocated fashion. When collocated, the JOINs are
+ executed on the local data available on each node without having to move large data sets
+ across the network. Such collocated approach provides the best scalability and performance
+ in distributed clusters.
</p>
</div>
<div class="col-sm-6 col-md-5 col-xs-12" style="padding-right:0">
@@ -76,9 +83,8 @@ under the License.
</div>
</div>
<p>
- Check <a href="/features/sql.html">SQL</a> and
- <a href="/features/datagrid.html" class="text-nowrap">Data Grid</a> features sections
- for more technical details.
+ You should also check Ignite <a href="/features/sql.html">SQL</a> and
+ <a href="/features/datagrid.html" class="text-nowrap">Data Grid</a> features.
</p>
</section>
</main>