You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by dm...@apache.org on 2017/08/25 22:15:28 UTC
svn commit: r1806246 - in /ignite/site/trunk: features/sql.html
use-cases/database/distributed-database.html
use-cases/database/in-memory-database.html
use-cases/database/key-value-database.html
use-cases/database/sql-database.html
Author: dmagda
Date: Fri Aug 25 22:15:28 2017
New Revision: 1806246
URL: http://svn.apache.org/viewvc?rev=1806246&view=rev
Log:
fixed artices
Modified:
ignite/site/trunk/features/sql.html
ignite/site/trunk/use-cases/database/distributed-database.html
ignite/site/trunk/use-cases/database/in-memory-database.html
ignite/site/trunk/use-cases/database/key-value-database.html
ignite/site/trunk/use-cases/database/sql-database.html
Modified: ignite/site/trunk/features/sql.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1806246&r1=1806245&r2=1806246&view=diff
==============================================================================
Binary files - no diff available.
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=1806246&r1=1806245&r2=1806246&view=diff
==============================================================================
--- ignite/site/trunk/use-cases/database/distributed-database.html (original)
+++ ignite/site/trunk/use-cases/database/distributed-database.html Fri Aug 25 22:15:28 2017
@@ -63,13 +63,13 @@ under the License.
every cluster node will own a portion of the overall data set.
</p>
<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">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">Learn</a>
- when to use one type of persistence over another.
+ The data and indexes can be stored both in RAM and, optionally, on disk if
+ <a href="/features/persistence.html">Ignite Native Persistence</a> is enabled.
+ </p>
+ <p>
+ Ignite Persistent Store is a distributed ACID and SQL-compliant disk store that transparently
+ integrates with Ignite's durable memory as an optional disk layer storing data and indexes on
+ SSD, Flash, 3D XPoint, and other types of non-volatile storages.
</p>
</div>
@@ -106,7 +106,7 @@ under the License.
</p>
<div class="page-heading">Partitioning & Replication</div>
<p>
- Depending on configuration, Ignite can either partition or replicate data.
+ Depending on the configuration, Ignite can either partition or replicate data.
Unlike <code>REPLICATED</code> mode, where data is fully replicated across all nodes
in the cluster, in <code>PARTITIONED</code> mode Ignite will equally split the data across
multiple cluster nodes, allowing for staring TBs of data both in memory and on disk.
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=1806246&r1=1806245&r2=1806246&view=diff
==============================================================================
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Fri Aug 25 22:15:28 2017
@@ -59,8 +59,8 @@ under the License.
data processing APIs.
</p>
<p>
- The database is capable of storing data as well as indexes both in memory and on disk thanks to the
- <a href="/features/durablememory.html">Durable Memory</a> architecture.
+ 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.
Modified: ignite/site/trunk/use-cases/database/key-value-database.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/key-value-database.html?rev=1806246&r1=1806245&r2=1806246&view=diff
==============================================================================
--- ignite/site/trunk/use-cases/database/key-value-database.html (original)
+++ ignite/site/trunk/use-cases/database/key-value-database.html Fri Aug 25 22:15:28 2017
@@ -33,14 +33,15 @@ under the License.
<!DOCTYPE html>
<html>
<head>
- <link rel="canonical" href="https://ignite.apache.org/use-cases/database/key-value-database.html" />
+ <link rel="canonical" href="https://ignite.apache.org/use-cases/database/key-value-database.html"/>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Key-Value Store - Apache Ignite</title>
<link media="all" rel="stylesheet" href="/css/all.css?v=1.8">
<link href="https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css" rel="stylesheet">
<link media="all" rel="stylesheet" href="/css/syntaxhighlighter.css">
- <link href='https://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,600italic,700,700italic,800,800italic' rel='stylesheet' type='text/css'>
+ <link href='https://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,600italic,700,700italic,800,800italic'
+ rel='stylesheet' type='text/css'>
<!--#include virtual="/includes/sh.html" -->
</head>
@@ -54,62 +55,62 @@ 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>
- Regardless of API used in Apache Ignite, when it is time to store data within a distributed
- cluster the data will be kept in a form of key-value pairs. The pairs end up in
- a key-value store that can be viewed as a distributed partitioned hash map with
- every cluster node owning a portion of the overall data set.
+ Ignite comes with a powerful a <strong>Key-Value Store</strong>
+ (a.k.a. <strong>Key-Value Database</strong>). It can be viewed as a distributed
+ partitioned hash map with every cluster node owning a portion of the overall data set.
</p>
<p>
- Apache Ignite fully complies with <a href="/use-cases/caching/jcache-provider.html" target="_blank">
- JCache (JSR 107)</a> specification providing extended features on top such as
- distributed ACID transactions, scan and continuous queries, collocated processing.
+ Ignite key-value store complies with
+ <a href="/use-cases/caching/jcache-provider.html">JCache (JSR 107)</a> specification and
+ provides
+ distributed ACID transactions, scan and continuous queries, collocated processing and more.
</p>
+ <div class="page-heading">Partitioning & Replication</div>
<p>
- This exceptional features coverage made Apache Ignite one of the most widely used <b>key-value
- store</b>. Let's look over its main characteristics.
+ Depending on the configuration, Ignite can either partition or replicate data.
+ Unlike <code>REPLICATED</code> mode, where data is fully replicated across all nodes
+ in the cluster, in <code>PARTITIONED</code> mode Ignite will equally split the data across
+ multiple cluster nodes, allowing for storing TBs of data both in memory and on disk.
</p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0">
<img class="img-responsive" src="/images/ignite-db-cache.png" width="400px" style="float:right;"/>
</div>
- </div>
+ </div>
- <div class="page-heading">Partitioning & Replication</div>
- <p>
- Depending on configuration, Ignite can either partition or replicate data.
- Unlike <code>REPLICATED</code> mode, where data is fully replicated across all nodes
- in the cluster, in <code>PARTITIONED</code> mode Ignite will equally split the data across
- multiple cluster nodes, allowing for storing TBs of data both in memory and on disk.
- </p>
- <div class="page-heading">Redundancy</div>
- <p>
- Ignite also allows to configure multiple <b>backup copies</b> to guarantee data resiliency
- in case of failures.
- </p>
- <div class="page-heading">Consistency</div>
- <p>
- Regardless of which replication scheme is used, Ignite guarantees data consistency across
- all cluster members.
- </p>
- <div class="page-heading">Performance and Durability</div>
- <p>
- Data can be stored both in RAM and on disk thanks to the
- <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>
- when to use one type of persistence over another.
- </p>
- <div class="page-heading">Data Locality</div>
- <p>
- Unlike other key-value databases, Ignite determines data locality using a pluggable hashing algorithm.
- Every client can determine which node a key belongs to by plugging it into a hashing function,
- without a need for any special mapping servers or name nodes.
- </p>
- <p>
- Check <a href="/features/datagrid.html" class="text-nowrap"><b>Data Grid</b></a>
- for more information.
- </p>
+ <div class="page-heading">Redundancy</div>
+ <p>
+ Ignite also allows to configure multiple <b>backup copies</b> to guarantee data resiliency
+ in case of failures.
+ </p>
+ <div class="page-heading">Consistency</div>
+ <p>
+ Regardless of which replication scheme is used, Ignite guarantees data consistency across
+ all cluster members.
+ </p>
+ <div class="page-heading">Performance and Durability</div>
+ <p>
+ Data can be stored both in RAM and, optionally, on disk if
+ <a href="/features/persistence.html">Ignite Native Persistence</a> is enabled.
+ </p>
+ <!--<div class="page-heading">External Databases</div>-->
+ <p>
+ Ignite also can automatically utilize 3rd party databases as storage, including integration with
+ most RDBMS, NoSQL or Hadoop systems.
+ </p>
+ <p>
+ <a href="https://apacheignite.readme.io/docs/distributed-persistent-store" target="_blank">Learn More</a>
+ </p>
+ <div class="page-heading">Data Locality</div>
+ <p>
+ Unlike other key-value databases, Ignite determines data locality using a pluggable hashing algorithm.
+ Every client can determine which node a key belongs to by plugging it into a hashing function,
+ without a need for any special mapping servers or name nodes.
+ </p>
+ <p>
+ Check <a href="/features/datagrid.html" class="text-nowrap"><b>Data Grid</b></a>
+ for more information.
+ </p>
</section>
</main>
Modified: ignite/site/trunk/use-cases/database/sql-database.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/sql-database.html?rev=1806246&r1=1806245&r2=1806246&view=diff
==============================================================================
--- ignite/site/trunk/use-cases/database/sql-database.html (original)
+++ ignite/site/trunk/use-cases/database/sql-database.html Fri Aug 25 22:15:28 2017
@@ -67,12 +67,12 @@ under the License.
<div class="page-heading">Performance and Durability</div>
<p>
- Data sets as well as indexes can be stored both in memory and on disk thanks to the
- <a href="/features/durablememory.html">Durable Memory</a>
- architecture. This allows executing distributed SQL operations across different memory layers
+ 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 operations across different memory layers
achieving in-memory performance with the durability of disk.
If the <a href="/features/persistence.html">disk layer</a>
- is disabled Apache Ignite can be used as a pure distributed
+ is disabled Apache Ignite can be utilized as an
<a href="/use-cases/database/in-memory-database.html"><b>in-memory</b> database</a>.
</p>
</div>