Author: dmagda
Date: Thu Aug 24 00:04:14 2017
New Revision: 1805979
URL: http://svn.apache.org/viewvc?rev=1805979&view=rev
Log:
prepared Ignite for NoSQL users page
Modified:
ignite/site/ignite-6036/use-cases/comparison/ignite-for-nosql.html
ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html
ignite/site/ignite-6036/use-cases/database/key-value-database.html
Modified: ignite/site/ignite-6036/use-cases/comparison/ignite-for-nosql.html
URL:
http://svn.apache.org/viewvc/ignite/site/ignite-6036/use-cases/comparison/ignite-for-nosql.html?rev=1805979&r1=1805978&r2=1805979&view=diff
==============================================================================
--- ignite/site/ignite-6036/use-cases/comparison/ignite-for-nosql.html
(original)
+++ ignite/site/ignite-6036/use-cases/comparison/ignite-for-nosql.html Thu Aug
24 00:04:14 2017
@@ -55,19 +55,15 @@ under the License.
<div style="padding:0 0 20px 0;">
<p>
Apache Ignite as many other NoSQL databases is
horizontally scalable, highly available and
- fault-tolerantdoes not require you as a skilled RDBMS user
to learn new APIs if you want to
- start working with an Ignite cluster. All the data
processing and SQL schema definition can
- be accomplished with a familiar SQL syntax. 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.
+ fault-tolerant. Ignite acts as a distributed partitioned
hash map making sure that every cluster
+ node owns a portion of the overall data set. This way the
more cluster nodes you add, the more data
+ you can store in the cluster.
</p>
<p>
- Ignite can store data and indexes both in memory and on
disk which allows executing distributed SQL
- queries across different memory layers achieving the
performance and scale of in-memory computing
- together with the disk durability and strong consistency
in one system. If the persistence is disabled
- Ignite can act as a pure <a
href="/use-cases/database/in-memory-database.html" target="_blank">
- in-memory database</a>.
+ Ignite can either partition or replicate the 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
+ <i>memory</i> and on <i>disk</i>.
</p>
</div>
@@ -181,21 +177,17 @@ under the License.
</section>
<p>
- The main difference between Ignite and traditional relational
databases is that, first, the memory is
- treated as a fully functional storage, not just as a caching
layer, like most databases do. Second,
- Ignite is horizontally scalable, highly available and supports
both
- <a href="/features/datagrid.html"
target="_blank">key-value</a> APIs and
- <a href="/collocatedprocessing.html"
target="_blank">collocated processing</a> approach.
+ Unlike eventually consistent NoSQL databases, Ignite can
operate in a <i>strongly consistent</i> mode,
+ guaranteeing the data consistency across all cluster nodes.
Ignite is a fully ACID-compliant platform.
</p>
-
-
<p>
- Check <a href="/features/sql.html" target="_blank">SQL</a>
section for more details or start using
- Ignite as a SQL database referring to
- <a
href="https://apacheignite.readme.io/docs/getting-started-sql";
target="_blank">SQL Getting Started Guide</a>.
- In addition, learn how Ignite is used for <a
href="/use-cases/caching/database-caching.html" target="_blank">
- relational databases acceleration</a>.
+ The other difference between Ignite and NoSQL databases is
that, first, the memory is
+ treated as a fully functional storage, not just as a caching
layer, like most databases do. Second,
+ in addition to
+ <a href="/features/datagrid.html"
target="_blank">key-value</a> APIs, Ignite supports
+ <a href="/features/sql.html" target="_blank">distributed
SQL</a> and
+ <a href="/collocatedprocessing.html"
target="_blank">collocated processing</a> approach.
</p>
</section>
</main>
Modified: ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html
URL:
http://svn.apache.org/viewvc/ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html?rev=1805979&r1=1805978&r2=1805979&view=diff
==============================================================================
--- ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html
(original)
+++ ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html Thu Aug
24 00:04:14 2017
@@ -186,9 +186,7 @@ under the License.
<a href="/features/datagrid.html"
target="_blank">key-value</a> APIs and
<a href="/collocatedprocessing.html"
target="_blank">collocated processing</a> approach.
</p>
-
-
-
+
<p>
Check <a href="/features/sql.html" target="_blank">SQL</a>
section for more details or start using
Ignite as a SQL database referring to
Modified: ignite/site/ignite-6036/use-cases/database/key-value-database.html
URL:
http://svn.apache.org/viewvc/ignite/site/ignite-6036/use-cases/database/key-value-database.html?rev=1805979&r1=1805978&r2=1805979&view=diff
==============================================================================
--- ignite/site/ignite-6036/use-cases/database/key-value-database.html
(original)
+++ ignite/site/ignite-6036/use-cases/database/key-value-database.html Thu Aug
24 00:04:14 2017
@@ -79,7 +79,7 @@ under the License.
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 staring TBs of data
both in memory and on disk.
+ multiple cluster nodes, allowing for storing TBs of data
both in memory and on disk.
</p>
<div class="page-heading">Redundancy</div>
<p>
