ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dma...@apache.org
Subject svn commit: r1805986 - /ignite/site/trunk/use-cases/database/distributed-database.html
Date Thu, 24 Aug 2017 01:19:59 GMT
Author: dmagda
Date: Thu Aug 24 01:19:59 2017
New Revision: 1805986

URL: http://svn.apache.org/viewvc?rev=1805986&view=rev
Log:
added distributed database use case

Modified:
    ignite/site/trunk/use-cases/database/distributed-database.html

Modified: ignite/site/trunk/use-cases/database/distributed-database.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/distributed-database.html?rev=1805986&r1=1805985&r2=1805986&view=diff
==============================================================================
--- ignite/site/trunk/use-cases/database/distributed-database.html (original)
+++ ignite/site/trunk/use-cases/database/distributed-database.html Thu Aug 24 01:19:59 2017
@@ -65,10 +65,10 @@ under the License.
                     <p>
                         When a piece of data is received by a cluster node, the node can
put it both in RAM and on disk
                         and process from two memory tiers equally well thanks to the
-                        <a href="/features/durablememory.html" target="_blank">Durable
Memory</a> architecture.
-                        The data can be persisted in <a href="/features/persistence.html"
target="_blank">
+                        <a href="/features/durablememory.html">Durable Memory</a>
architecture.
+                        The data can be persisted in <a href="/features/persistence.html">
                         Ignite Native Persistence</a> or in a 3rd party database such
as RDBMS, NoSQL or Hadoop.
-                        <a href="https://apacheignite.readme.io/docs/distributed-persistent-store"
target="_blank">Learn</a>
+                        <a href="https://apacheignite.readme.io/docs/distributed-persistent-store">Learn</a>
                         when to use one type of persistence over another.
                     </p>
                 </div>
@@ -83,15 +83,15 @@ under the License.
                 Ignite complies with SQL ANSI-99 standard supporting all <b>SQL</b>
and <b>DML</b> commands,
                 including SELECT, UPDATE, INSERT, MERGE, DELETE statements and distributed
joins. It also provides
                 support for a subset of <b>DDL</b> commands relevant for distributed
SQL databases. Read more about
-                Ignite's <a href="/use-cases/database/sql-database.html" target="_blank">SQL
capabilities</a>.
+                Ignite's <a href="/use-cases/database/sql-database.html">SQL capabilities</a>.
             </p>
 
             <div class="page-heading">Key-value</div>
             <p>
-                Apache Ignite key-value APIs are compliant with <a href="/use-cases/caching/jcache-provider.html"
target="_blank">
+                Apache Ignite key-value APIs are compliant with <a href="/use-cases/caching/jcache-provider.html">
                 JCache (JSR 107)</a> specification and provide extended features built
on top such as
                 distributed ACID transactions, scan and continuous queries, collocated processing.
Read more about
-                Ignite's <a href="/use-cases/database/key-value-database.html" class="text-nowrap"
target="_blank">
+                Ignite's <a href="/use-cases/database/key-value-database.html" class="text-nowrap">
                 key-value database (Data Grid) capabilities</a>.
             </p>
             <div class="page-heading">Collocated Processing</div>
@@ -102,7 +102,7 @@ under the License.
                 network is the most expensive operation in a distributed system.
             </p>
             <p>
-                A much more scalable approach is <a href="/collocatedprocessing.html"
target="_blank">
+                A much more scalable approach is <a href="/collocatedprocessing.html">
                 collocated processing</a> that reverses the flow by bringing the computations
to the servers where
                 the data actually resides. This approach allows you to execute advanced logic
or distributed SQL
                 with JOINs exactly where the data is stored avoiding expensive serialization
and network trips.
@@ -125,9 +125,9 @@ under the License.
                 all cluster members.
             </p>
             <p>
-                Check <a href="/features/sql.html" target="_blank">SQL</a>,
-                <a href="/features/datagrid.html" class="text-nowrap" target="_blank">Data
Grid</a>, and
-                <a href="/features/computegrid.html" class="text-nowrap" target="_blank">Compute
Grid</a>
+                Check <a href="/features/sql.html">SQL</a>,
+                <a href="/features/datagrid.html" class="text-nowrap">Data Grid</a>,
and
+                <a href="/features/computegrid.html" class="text-nowrap">Compute Grid</a>
                 features sections for more technical details.
             </p>
         </section>



Mime
View raw message