Author: dmagda
Date: Thu Jan 25 01:55:29 2018
New Revision: 1822172
URL: http://svn.apache.org/viewvc?rev=1822172&view=rev
Log:
updated what's ignite page
Modified:
ignite/site/trunk/whatisignite-2.html
Modified: ignite/site/trunk/whatisignite-2.html
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?rev=1822172&r1=1822171&r2=1822172&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite-2.html (original)
+++ ignite/site/trunk/whatisignite-2.html Thu Jan 25 01:55:29 2018
@@ -78,9 +78,9 @@ under the License.
<p class="ignite-facts-answer">
<strong>Yes</strong>. Even though Ignite durable
memory 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.<br/>
- <a href="/use-cases/database/in-memory-database.html"
target="_blank">Read more</a>
+ support for SQL and distributed joins.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/use-cases/database/in-memory-database.html">Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
@@ -88,9 +88,9 @@ under the License.
<p class="ignite-facts-answer">
<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.<br/>
- <a href="/features/datagrid.html" target="_blank">Read
more</a>
+ including any RDBMS or NoSQL stores.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/features/datagrid.html">Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
@@ -99,9 +99,9 @@ under the License.
<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.<br/>
- <a href="/use-cases/caching/database-caching.html"
target="_blank">Read more</a>
+ distribution modes, distributed ACID transactions, SQL
queries, native persistence, and more.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/use-cases/caching/database-caching.html">Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
@@ -110,9 +110,9 @@ under the License.
<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.<br/>
- <a
href="/use-cases/database/distributed-database.html" target="_blank">Read
more</a>
+ and collocate various pieces of data together for
efficiency.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/use-cases/database/distributed-database.html">Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
@@ -121,13 +121,9 @@ under the License.
<strong>Not fully</strong>. Although Ignite aims to
behave like any other relational SQL database,
there are differences in how Ignite handles
constraints and indexes. Ignite supports primary and
secondary indexes, however, the uniqueness can only be
enforced for the primary indexes.
- Ignite also does not support foreign key
constraints.<br/>
- <a href="/use-cases/database/sql-database.html"
target="_blank">Read more</a>
+ Ignite also does not support foreign key constraints.
</p>
- <!--<p>-->
- <!--Essentially, Ignite purposely does not support any
constraints that would entail a cluster-wide broadcast-->
- <!--message for each update and significantly hurt
performance and scalability of the system.-->
- <!--</p>-->
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/use-cases/database/sql-database.html">Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
@@ -136,17 +132,18 @@ under the License.
<strong>Both</strong>. Native persistence in Ignite
can be turned on and off. This allows Ignite to store
data sets bigger than can fit in the available memory.
Essentially, smaller operational data sets
can be stored in-memory only, and larger data sets
that do not fit in memory can be stored on disk,
- using memory as a caching layer for better
performance.<br/><br/> <br/>
+ using memory as a caching layer for better performance.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/features/persistence.html" target="_blank">Read more</a></p><br/><br/>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
<h3 class="ignite-facts-question">Is Ignite a NoSQL
database?</h3>
<p class="ignite-facts-answer">
<strong>Not exactly</strong>. Just like other NoSQL
databases, Ignite is highly available and
- horizontally scalable. However, unlike other NoSQL
databases, Ignite supports SQL and ACID transactions.<br/>
- <a href="/use-cases/comparison/ignite-for-nosql.html"
target="_blank">Read more</a>
+ horizontally scalable. However, unlike other NoSQL
databases, Ignite supports SQL and ACID transactions.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/use-cases/comparison/ignite-for-nosql.html">Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
@@ -158,6 +155,7 @@ under the License.
At SQL level Ignite supports atomic, but not yet
transactional consistency. Ignite community plans
to implement SQL transactions in version 2.5.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="https://apacheignite.readme.io/docs/transactions";>Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
@@ -166,17 +164,17 @@ under the License.
<strong>Yes</strong>. Ignite supports both, key-value
and SQL for modelling and accessing data.
In addition, Ignite provides strong processing APIs
for computing on distributed data.
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/use-cases/database/distributed-database.html">Read more</a></p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
<h3 class="ignite-facts-question">Is Ignite a key-value
store?</h3>
<p class="ignite-facts-answer">
<strong>Yes</strong>. Ignite provides a feature rich
key-value API, that is JCache (JSR-107) compliant
- and supports Java, C++, <nobr>and .NET.</nobr><br/>
- <a
href="/use-cases/database/key-value-store-database.html" target="_blank">Read
more</a>
+ and supports Java, C++, <nobr>and .NET.</nobr>
</p>
+ <p style="margin-top: 10px; padding-left: 10px"><a
href="/use-cases/database/key-value-store-database.html">Read
more</a></p><br/><br/>
</div>
-
<h3 style="color: black;">Book</h3>
<p>Learn even more from <a href="http://a.co/h4MBi1v";
target="_blank">High-Performance in-memory computing with Apache Ignite</a>
book.</p>
</section>
