This is an automated email from the ASF dual-hosted git repository.
dmagda pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ignite-website.git
The following commit(s) were added to refs/heads/master by this push:
new 64068f9 Updated text of the in-memory data grid page.
64068f9 is described below
commit 64068f9eb127c10f04b6987208642e43a364e77a
Author: Denis Magda <dma...@gridgain.com>
AuthorDate: Mon Apr 20 10:51:16 2020 -0700
Updated text of the in-memory data grid page.
---
use-cases/in-memory-data-grid.html | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/use-cases/in-memory-data-grid.html
b/use-cases/in-memory-data-grid.html
index 3c15af3..97abdf6 100644
--- a/use-cases/in-memory-data-grid.html
+++ b/use-cases/in-memory-data-grid.html
@@ -59,21 +59,20 @@ under the License.
<p>
The Apache Ignite® in-memory data grid accelerates and scales your
databases, services,
and APIs. It supports key-value and ANSI SQL APIs, ACID
transactions, co-located processing,
- and machine learning libraries. Ignite is frequently used to
increase the performance and
- scalability of real-time applications, as a <a
href="/use-cases/digital-integration-hub.html">digital integration hub</a> to
provide real-time data
- access to one or many applications to data from one or many siloed
data sources, for <a href="/use-cases/high-performance-computing.html">high
- performance computing</a>, or for data caching.
+ and machine learning libraries. As an in-memory data grid, Ignite
is frequently used to increase the performance and
+ scalability of existing real-time applications, for <a
href="/use-cases/high-performance-computing.html">
+ high-performance computing</a>, or for caching of data scattered
across databases.
</p>
<img class="img-fluid diagram-right"
src="/images/svg-diagrams/data_grid.svg" alt="In-Memory Data Grid with Apache
Ignite"/>
<h2>What is an In-Memory Data Grid?</h2>
<p>An in-memory data grid is a read-through/write-through caching
strategy in which the application
- layer treats the data grid as the primary data store. The application
layer writes to and reads
- from the in-memory data grid. The in-memory data grid ensures that any
underlying databases stay
+ layer treats the data grid as the primary data store. Applications
write to and read
+ from the in-memory cluster that propagates all the changes to any
underlying databases automatically keeping them
updated and consistent with the in-memory data.</p>
- <p>The Ignite in-memory data grid provides all essential APIs needed
to simplify its adoption. The
+ <p>Ignite as an in-memory data grid provides all essential APIs needed
to simplify its adoption. The
APIs include <a href="/use-cases/key-value-store.html">distributed
key-value</a> and <a href="/features/sql.html">ANSI SQL</a> queries, <a
href="/features/acid-transactions.html">ACID transactions</a>, <a
href="/features/collocated-processing.html">co-located processing</a>,
and <a href="/features/machinelearning.html">machine learning</a>
models. While key-value and SQL calls let you request, join, and group
distributed data sets, the compute and machine learning components
help to eliminate data
@@ -82,10 +81,10 @@ under the License.
<p>Ignite can store data both in memory and on disk with two options
for data persistence. You
can persist changes in an external database or have Ignite keep data
in its <a href="/arch/native-persistence.html">native persistence</a>. </p>
- <h2>IGNITE in-memory data grid AND EXTERNAL DATABASES</h2>
+ <h2>IGNITE as an in-memory data grid AND EXTERNAL DATABASES</h2>
- <p>The Ignite in-memory data grid can improve the performance and
scalability of any external
- database such as RDBMS, NoSQL or Hadoop, by sliding in as an
in-memory cache between the
+ <p>Ignite can improve the performance and scalability of any external
+ database such as RDBMS, NoSQL or Hadoop, by sliding in as an
in-memory data grid between the
application and the database layer. When an application writes
data to the cache, Ignite
automatically writes-through or writes-behind all data
modifications to the underlying
external store. Ignite also performs ACID transactions where it
coordinates and commits
