Author: dmagda
Date: Thu Sep 14 21:54:49 2017
New Revision: 1808398
URL: http://svn.apache.org/viewvc?rev=1808398&view=rev
Log:
shifted paragraphs a bit
Modified:
ignite/site/trunk/features/datagrid.html
Modified: ignite/site/trunk/features/datagrid.html
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808398&r1=1808397&r2=1808398&view=diff
==============================================================================
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Thu Sep 14 21:54:49 2017
@@ -71,42 +71,44 @@ under the License.
Ignite Data Grid is lightning fast and is one of the
fastest implementations of transactional or
atomic data in distributed clusters today. We know it
because we constantly benchmark it ourselves.
</p>
- <p>
- The data in the data grid can be stored only in
memory, or can also be persisted to disk.
- If <a href="/features/persistence.html"
target="_blank">Ignite native persistence</a> is enabled,
- then data and indexes will be persisted natively by
Ignite on every cluster node. In this case,
- memory only serves as a smaller caching layer of the
overall persisted data set. All queries and transactions
- span the whole data set stored on disk.
- </p>
- <p>
- The in-memory data grid can also improve performance
and scalability by integrating with existing 3rd party
- databases, like RDBMS, NoSQL, or Hadoop-based
storages. This approach does not require
- rip-and-replace of the existing data, but has its
limitations. For example, SQL or scan queries will only include the
- results stored in memory, and not in the external
database, since Ignite does not have any knowledge of the external data.
- </p>
- <p>
- <a
href="https://apacheignite.readme.io/docs/distributed-persistent-store";
target="_blank">Read more</a>
- about different types of persistence in Ignite.
- </p>
-
- <div class="videos">
- <div class="page-heading">Videos:</div>
- <ul class="page-list">
- <li>
- <i class="fa fa-lg fa-play-circle-o"></i>
- <span class="video-title">
- <a target="youtube"
href="https://www.youtube.com/watch?v=pFbDWpOiMOU";>Getting Started with Data
Grid</a>
- </span>
- <span class="video-duration">03:49</span>
- </li>
- </ul>
- </div>
</div>
<div class="col-sm-6 col-md-5 col-xs-12"
style="padding-right:0">
<img class="img-responsive"
src="/images/ignite-db-cache.png" width="400px" style="float:right;"/>
</div>
</div>
+
+ <p>
+ The data in the data grid can be stored only in memory, or can
also be persisted to disk.
+ If <a href="/features/persistence.html" target="_blank">Ignite
native persistence</a> is enabled,
+ then data and indexes will be persisted natively by Ignite on
every cluster node. In this case,
+ memory only serves as a smaller caching layer of the overall
persisted data set. All queries and transactions
+ span the whole data set stored on disk.
+ </p>
+ <p>
+ The in-memory data grid can also improve performance and
scalability by integrating with existing 3rd party
+ databases, like RDBMS, NoSQL, or Hadoop-based storages. This
approach does not require
+ rip-and-replace of the existing data, but has its limitations.
For example, SQL or scan queries will only include the
+ results stored in memory, and not in the external database,
since Ignite does not have any knowledge of the external data.
+ </p>
+ <p>
+ <a
href="https://apacheignite.readme.io/docs/distributed-persistent-store";
target="_blank">Read more</a>
+ about different types of persistence in Ignite.
+ </p>
+
+ <div class="videos">
+ <div class="page-heading">Videos:</div>
+ <ul class="page-list">
+ <li>
+ <i class="fa fa-lg fa-play-circle-o"></i>
+ <span class="video-title">
+ <a target="youtube"
href="https://www.youtube.com/watch?v=pFbDWpOiMOU";>Getting Started with Data
Grid</a>
+ </span>
+ <span class="video-duration">03:49</span>
+ </li>
+ </ul>
+ </div>
+
<div class="code-examples">
<div class="page-heading">Code Examples:</div>
<!-- Nav tabs -->
