Author: dmagda
Date: Mon Jan 29 21:58:20 2018
New Revision: 1822588
URL: http://svn.apache.org/viewvc?rev=1822588&view=rev
Log:
updated what's ignite page
Removed:
ignite/site/trunk/whatisignite-2.html
ignite/site/trunk/whatisignite-3.html
ignite/site/trunk/whatisignite-4.html
Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/scss/ignite.scss
ignite/site/trunk/whatisignite.html
Modified: ignite/site/trunk/css/all.css
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1822588&r1=1822587&r2=1822588&view=diff
==============================================================================
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Mon Jan 29 21:58:20 2018
@@ -9384,7 +9384,7 @@ div.square {
#whatisignite .img-holder {
width: 100%;
height: 100%;
- margin-bottom: 80px;
+ margin-bottom: 30px;
}
#whatisignite .img-holder img {
display: block;
@@ -9490,9 +9490,11 @@ div.square {
}
#ignite-facts > .fact-panel > .left {
padding-left: 0px;
+ padding-right: 15px;
}
#ignite-facts > .fact-panel > .right {
padding-right: 0px;
+ padding-left: 15px;
}
#ignite-facts > .fact-panel hr {
border-top: none !important;
@@ -9504,36 +9506,6 @@ div.square {
.ignite-facts-question {
margin-bottom: 10px;
- /*padding-left: 10px !important;*/
-}
-
-.ignite-facts-question-red {
- background: #e50000;
- border-radius: 7px;
- margin-bottom: 10px;
- padding-left: 10px !important;
-}
-
-.ignite-facts-answer {
- /*padding-left: 10px !important;*/
- /*padding-right: 10px !important;*/
-}
-
-#ignite-facts-3 > .fact-panel {
- background: #efefef;
- padding: 20px 20px 0 20px;
- margin-bottom: 40px;
-}
-#ignite-facts-3 > .fact-panel h3 {
- line-height: 30px;
- padding-bottom: 10px;
- padding-top: 10px;
-}
-#ignite-facts-3 > .left {
- border-right: solid white 10px;
-}
-#ignite-facts-3 > .right {
- border-left: solid white 10px;
}
.btn-transparent {
Modified: ignite/site/trunk/scss/ignite.scss
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1822588&r1=1822587&r2=1822588&view=diff
==============================================================================
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Mon Jan 29 21:58:20 2018
@@ -1951,7 +1951,7 @@ div.square {
.img-holder {
width:100%;
height:100%;
- margin-bottom: 80px;
+ margin-bottom: 30px;
}
.img-holder img {
@@ -2070,10 +2070,12 @@ div.square {
> .left {
padding-left: 0px;
+ padding-right: 15px;
}
> .right {
padding-right: 0px;
+ padding-left: 15px;
}
hr {
@@ -2090,40 +2092,4 @@ div.square {
.ignite-facts-question {
margin-bottom: 10px;
- /*padding-left: 10px !important;*/
}
-
-.ignite-facts-question-red {
- background: #e50000;
- border-radius: 7px;
- margin-bottom: 10px;
- padding-left: 10px !important;
-}
-
-.ignite-facts-answer {
- /*padding-left: 10px !important;*/
- /*padding-right: 10px !important;*/
-}
-
-
-#ignite-facts-3 {
- > .fact-panel {
- background: #efefef;
- padding: 20px 20px 0 20px;
- margin-bottom: 40px;
-
- h3 {
- line-height: 30px;
- padding-bottom: 10px;
- padding-top: 10px;
- }
- }
-
- > .left {
- border-right: solid white 10px;
- }
-
- > .right {
- border-left: solid white 10px;
- }
-}
\ No newline at end of file
Modified: ignite/site/trunk/whatisignite.html
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1822588&r1=1822587&r2=1822588&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Mon Jan 29 21:58:20 2018
@@ -52,172 +52,150 @@ under the License.
<!--#include virtual="/includes/header.html" -->
<main id="main" role="main" class="container">
- <section id="whatisignite" class="page-section" style="border: none;">
- <h1 class="first heading" style="text-align: center;"><span>Apache
Ignite™ is ...</span></h1>
- <div class="col-sm-12 col-md-12 col-xs-12 description-block">
- <p style="text-align: center;"><i>memory-centric distributed
- <strong>database</strong>, <strong>caching</strong>, and
<strong>processing</strong> platform for
- transactional, analytical, and streaming workloads,<br/>
- delivering <nobr>in-memory</nobr> speeds at petabyte
scale</i>
- </p>
+ <div class="col-sm-12 col-md-12 col-xs-12" style="padding: 0px;">
+ <section id="whatisignite" class="page-section" style="border:
none;">
+ <h1 class="first heading" style="text-align:
center;"><span>Apache Ignite™ is ...</span></h1>
+ <div class="col-sm-12 col-md-12 col-xs-12 description-block">
+ <p style="text-align: center;"><i>memory-centric
distributed
+ <strong>database</strong>, <strong>caching</strong>,
and <strong>processing</strong> platform <br/>
+ for transactional, analytical, and streaming
workloads,<br/>
+ delivering <nobr>in-memory</nobr> speeds at petabyte
scale</i>
+ </p>
+ </div>
+ <div class="col-sm-12 col-md-12 col-xs-12 img-holder">
+ <a href="/images/durable-memory.png"><img
class="img-responsive" src="/images/ignite_architecture.png" alt="Apache Ignite
Architecture" width="600px;"/></a>
+ </div>
+ </section>
+ </div>
+ <div class="col-sm-12 col-md-12 col-xs-12" style="top: -50px; padding:
0px;">
+ <div class="section-heading">
+ <h2 style="text-align: center;">IGNITE FACTS</h2>
</div>
- <div class="col-sm-12 col-md-12 col-xs-12 img-holder">
- <a href="/images/durable-memory.png"><img
class="img-responsive" src="/images/durable-memory.png" alt="Apache Ignite -
Durable Memory" width="900px;"/></a>
- </div>
- </section>
-
- <section id="whatisignite-feature-desc" class="page-section"
style="border: none;">
- <div class="col-sm-12 col-md-12 col-xs-12">
- <h3>Durable Memory</h3>
- <p>
- Ignite's durable memory component treats RAM not just as a
caching layer but as a complete fully functional storage layer.
- This means that users can turn the persistence on and off
as needed. If the persistence is off, then Ignite
- can act as a distributed <nobr><i><a
href="/use-cases/database/in-memory-database.html">in-memory
database</a></i></nobr> or <nobr><i><a href="/features/datagrid.html">in-memory
data grid</a></i></nobr>,
- depending on whether you prefer to use SQL or key-value
APIs. If the persistence is turned on, then Ignite becomes a distributed,
- <nobr><i><a href="/features/sql.html">horizontally
scalable database</a></i></nobr> that guarantees full data consistency and is
- resilient to full cluster failures.
- </p>
- <h3>Ignite Persistence</h3>
- <p>
- Ignite <a href="/features/persistence.html">native
persistence</a> is a distributed,
- strongly consistent disk store that transparently
integrates with Ignite's <i>durable memory</i>.
- </p>
- <h3>ACID Compliance</h3>
- <p>
- Data stored in Ignite is ACID-compliant both in memory and
on disk, making Ignite a <i><strong>strongly consistent</strong></i> system.
- Ignite transactions work across the network and can span
multiple servers.
- </p>
-
- <h3>Complete SQL Support</h3>
- <p>
- Ignite provides full support for SQL, DDL and DML,
allowing users to interact with Ignite using pure SQL without writing any code.
- This means that users can create tables and indexes as
well as insert, update, and query data using only SQL. Having such complete SQL
support makes Ignite a one-of-a-kind
- <i><a href="/features/sql.html">distributed SQL
database</a></i>.
- </p>
-
- <h3>Key-Value</h3>
- <p>
- The in-memory data grid component in Ignite is a fully
transactional <i><a href="/use-cases/database/key-value-store.html">distributed
key-value store</a></i> that can scale horizontally
- across 100s of servers in the cluster. When persistence is
enabled, Ignite can also store more data than fits in memory and survive full
cluster restarts.
- </p>
-
- <h3>Collocated Processing</h3>
- <p>
- Most traditional databases work in a client-server
fashion, meaning that data must be brought to the client side for processing.
This approach requires
- lots of data movement from servers to clients and
generally does not scale. Ignite, on the other hand, allows for sending
light-weight computations to the data,
- i.e. <nobr><i><a
href="/collocatedprocessing.html">collocating computations with
data</a></i></nobr>. As a result, Ignite scales better and minimizes data
movement.
- </p>
-
- <h3>Scalability and Durability</h3>
- <p>
- Ignite is an elastic, horizontally scalable distributed
system that supports adding and removing cluster nodes on demand. Ignite also
allows for
- storing multiple copies of the data, making it resilient
to partial cluster failures. If the persistence is enabled, then data stored in
Ignite
- will also survive full cluster failures. Cluster restarts
in Ignite can be very fast, as the data becomes operational instantaneously
directly from disk.
- As a result, the data does not need to be preloaded
in-memory to begin processing, and Ignite caches will lazily warm up resuming
the in memory performance.
- </p>
- </div>
- </section>
-
- <section id="ignite-faq" class="page-section">
- <div class="col-sm-12 col-md-12 col-xs-12" style="margin-top:
20px;">
- <h2 style="text-align: center; color: #e50000;">Ignite
Facts</h2>
- <hr><br/><br/><br/>
-
- <h3>Is Ignite a persistent or memory-only storage?</h3>
- <p>
- <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.
-
- </p>
- <br/><br/>
-
- <h3>Is Ignite an in-memory database (IMDB)?</h3>
- <p>
- <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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite an in-memory data grid (IMDG)?</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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a distributed cache?</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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a distributed database?</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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite an SQL database?</h3>
- <p>
- <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.
- </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>
- <br/><br/>
-
- <h3>Is Ignite a NoSQL database?</h3>
- <p>
- <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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a transactional database?</h3>
- <p>
- <strong>Not fully</strong>. ACID Transactions are
supported, but only at key-value API level.
- Ignite also supports cross-partition transactions, which
means that transactions can span keys
- residing in different partitions on different servers.
- </p>
-
- <p>
- At SQL level Ignite supports atomic, but not yet
transactional consistency. Ignite community plans
- to implement SQL transactions in version 2.5.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a multi-model database?</h3>
- <p>
- <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>
- <br/><br/>
-
- <h3>Is Ignite a key-value store?</h3>
- <p>
- <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>
- </p>
- <p><a
href="https://apacheignite.readme.io/docs/data-grid";></a></p><br/><br/>
-
- <h3>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>
- </div>
- </section>
+ <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>
+ <p>
+ <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.
+ </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 an
in-memory data grid?</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.
+ </p>
+ <p style="margin-top: 10px;">Read more: <a
href="/features/datagrid.html">Data Grid</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>
+ <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.
+ </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 a
distributed database?</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.
+ </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 an SQL
database?</h3>
+ <p>
+ <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.
+ </p>
+ <p style="margin-top: 10px;">Read more: <a
href="/use-cases/database/sql-database.html">SQL Database</a></p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 right">
+ <h3 class="ignite-facts-question">Is Ignite a disk or
memory-only storage?</h3>
+ <p>
+ <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.
+ </p>
+ <p style="margin-top: 10px;">Read more: <a
href="/features/persistence.html" target="_blank">Native
Persistence</a></p><br/><br/>
+ </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 NoSQL
database?</h3>
+ <p>
+ <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.
+ </p>
+ <p style="margin-top: 10px;">Read more: <a
href="/use-cases/comparison/ignite-for-nosql.html">Ignite for NoSQL</a></p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 right">
+ <h3 class="ignite-facts-question">Is Ignite a
transactional database?</h3>
+ <p>
+ <strong>Not fully</strong>. ACID Transactions are
supported, but only at key-value API level.
+ Ignite also supports cross-partition transactions,
which means that transactions can span keys
+ residing in different partitions on different
servers. <br/> <br/>
+ 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;">Read more: <a
href="https://apacheignite.readme.io/docs/transactions";>ACID
Transactions</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
multi-model database?</h3>
+ <p>
+ <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;">Read more: <a
href="/use-cases/database/distributed-database.html">Distributed
Database</a></p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 right">
+ <h3 class="ignite-facts-question">Is Ignite a
key-value store?</h3>
+ <p>
+ <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>
+ </p>
+ <p style="margin-top: 10px;">Read more: <a
href="/use-cases/database/key-value-store-database.html">Key-Value
Store</a></p><br/><br/>
+ </div>
+ </div>
+ <div class="col-sm-12 col-md-12 col-xs-12 fact-panel">
+ <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>
+ </div>
+ </section>
+ </div>
</main>
<!--#include virtual="/includes/footer.html" -->
