ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dsetrak...@apache.org
Subject svn commit: r1843616 - /ignite/site/trunk/whatisignite.html
Date Fri, 12 Oct 2018 01:37:26 GMT
Author: dsetrakyan
Date: Fri Oct 12 01:37:26 2018
New Revision: 1843616

URL: http://svn.apache.org/viewvc?rev=1843616&view=rev
Log:
Minor fix.

Modified:
    ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1843616&r1=1843615&r2=1843616&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Fri Oct 12 01:37:26 2018
@@ -74,50 +74,48 @@ under the License.
             <hr>
             <section id="ignite-facts" class="page-section">
                 <div class="col-sm-12 col-md-12 col-xs-12 fact-panel">
+                    
                     <div class="col-sm-6 col-md-6 col-xs-12  left">
-                        <h3 class="ignite-facts-question">Is Ignite an in-memory database?</h3>
+
+                        <h3 class="ignite-facts-question">Is Ignite a distributed cache?</h3>
                         <p>
-                            <strong>Yes</strong>. Even though Ignite memory-centric
storage works well in-memory and on-disk, the disk
-                            persistence can be disabled and Ignite can act as a distributed
in-memory database, with
-                            support for SQL and distributed joins.
+                            <strong>Yes</strong>. When native persistence is
disabled, Ignite becomes a distributed in-memory cache
+                            with support for JCache specification (JSR 107), distributed
ACID transactions,
+                            SQL queries, on-disk persistence, and more.
                         </p>
-                        <p style="margin-top: 10px;">Read more: <a href="/use-cases/database/in-memory-database.html">In-Memory
Database</a></p>
+                        <p style="margin-top: 10px;">Read more: <a href="/use-cases/caching/database-caching.html">Database
Caching</a></p>
                     </div>
 
                     <div class="col-sm-6 col-md-6 col-xs-12  right">
-                        <h3 class="ignite-facts-question">Is Ignite an in-memory data
grid?</h3>
+                        <h3 class="ignite-facts-question">Is Ignite a distributed database?</h3>
                         <p>
-                            <strong>Yes</strong>. Ignite is a full-featured distributed
key-value data grid, which can be used either in
-                            memory-only mode or with Ignite native persistence. It can also
automatically integrate with any 3rd party databases,
-                            including any RDBMS or NoSQL stores.
+                            <strong>Yes</strong>. Ignite is a strongly consistent
distributed database. Data in Ignite is
+                            stored in-memory and/or on-disk and is either partitioned or
replicated across a cluster of
+                            multiple nodes. This provides for scalability, performance, and
resiliency.
                         </p>
-                        <p style="margin-top: 10px;">Read more: <a href="/features/datagrid.html">In-Memory
Data Grid</a></p>
+                        <p style="margin-top: 10px;">Read more: <a href="/use-cases/database/distributed-database.html">Distributed
Database</a></p>
                     </div>
                 </div>
 
                 <div class="col-sm-12 col-md-12 col-xs-12 fact-panel">
-                    
                     <div class="col-sm-6 col-md-6 col-xs-12  left">
-
-                        <h3 class="ignite-facts-question">Is Ignite a distributed cache?</h3>
+                        <h3 class="ignite-facts-question">Is Ignite an in-memory database?</h3>
                         <p>
-                            <strong>Yes</strong>. When native persistence is
disabled, Ignite becomes a distributed cache.
-                            Ignite implements JCache specification (JSR 107) and provides
-                            a lot more functionality than required by the specification,
including partitioned and replicated
-                            distribution modes, distributed ACID transactions, SQL queries,
native persistence, and more.
+                            <strong>Yes</strong>. Even though Ignite memory-centric
storage works well in-memory and on-disk, the disk
+                            persistence can be disabled and Ignite can act as a distributed
in-memory database, with
+                            support for SQL and distributed joins.
                         </p>
-                        <p style="margin-top: 10px;">Read more: <a href="/use-cases/caching/database-caching.html">Database
Caching</a></p>
+                        <p style="margin-top: 10px;">Read more: <a href="/use-cases/database/in-memory-database.html">In-Memory
Database</a></p>
                     </div>
 
                     <div class="col-sm-6 col-md-6 col-xs-12  right">
-                        <h3 class="ignite-facts-question">Is Ignite a distributed database?</h3>
+                        <h3 class="ignite-facts-question">Is Ignite an in-memory data
grid?</h3>
                         <p>
-                            <strong>Yes</strong>. Data in Ignite is either partitioned
or replicated across a cluster of
-                            multiple nodes. This provides scalability and adds resiliency
to the system. Ignite automatically
-                            controls how data is partitioned, however, users can plugin their
own distribution (affinity) functions
-                            and collocate various pieces of data together for efficiency.
+                            <strong>Yes</strong>. Ignite is a full-featured distributed
key-value data grid, which can be used either in
+                            memory-only mode or with Ignite native persistence. It can also
automatically integrate with any 3rd party databases,
+                            including any RDBMS or NoSQL stores.
                         </p>
-                        <p style="margin-top: 10px;">Read more: <a href="/use-cases/database/distributed-database.html">Distributed
Database</a></p>
+                        <p style="margin-top: 10px;">Read more: <a href="/features/datagrid.html">In-Memory
Data Grid</a></p>
                     </div>
                 </div>
 



Mime
View raw message