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/09/13 19:28:28 UTC
svn commit: r1808276 - in /ignite/site/trunk: css/all.css scss/ignite.scss
whatisignite-2.html whatisignite.html
Author: dmagda
Date: Wed Sep 13 19:28:27 2017
New Revision: 1808276
URL: http://svn.apache.org/viewvc?rev=1808276&view=rev
Log:
updated what's ignite page
Removed:
ignite/site/trunk/whatisignite-2.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=1808276&r1=1808275&r2=1808276&view=diff
==============================================================================
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Wed Sep 13 19:28:27 2017
@@ -9167,7 +9167,11 @@ hr.vertical {
}
#ignite-faq h2 {
- font-size: 30px;
+ font-size: 32px;
+}
+#ignite-faq h3 {
+ font-size: 28px;
+ line-height: 40px;
}
.header {
@@ -9225,8 +9229,7 @@ div.square {
}
#whatisignite .description-block {
padding: 0px;
- height: 250px;
- margin-bottom: 60px;
+ margin-bottom: 30px;
}
@media (max-width: 992px) {
#whatisignite .description-block {
@@ -9249,30 +9252,9 @@ div.square {
margin-top: 20px;
}
}
-#whatisignite .description-block-2 {
- padding: 0px;
- margin-bottom: 30px;
-}
-@media (max-width: 992px) {
- #whatisignite .description-block-2 {
- height: auto;
- margin-bottom: 50px;
- }
-}
-#whatisignite .description-block-2 .ignite-image {
- padding-right: 0;
- top: -115px;
-}
-@media (max-width: 992px) {
- #whatisignite .description-block-2 .ignite-image {
- top: auto;
- }
-}
-@media (max-width: 767px) {
- #whatisignite .description-block-2 .ignite-image {
- top: auto;
- margin-top: 20px;
- }
+#whatisignite .description-block p {
+ font-size: 28px;
+ line-height: 40px;
}
#whatisignite .img-holder {
width: 100%;
@@ -9331,9 +9313,12 @@ div.square {
}
}
+#whatisignite-feature-desc h2 {
+ font-size: 32px;
+}
#whatisignite-feature-desc h3 {
- font-size: 30px;
- padding-top: 20px;
+ font-size: 28px;
+ line-height: 40px;
}
#whatisignite-feature-desc p {
padding-bottom: 30px;
Modified: ignite/site/trunk/scss/ignite.scss
URL: http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1808276&r1=1808275&r2=1808276&view=diff
==============================================================================
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Wed Sep 13 19:28:27 2017
@@ -1718,8 +1718,14 @@ hr.vertical {
}
#ignite-faq {
+
h2 {
- font-size: 30px;
+ font-size: 32px;
+ }
+
+ h3 {
+ font-size: 28px;
+ line-height: 40px;
}
}
@@ -1778,31 +1784,6 @@ div.square {
}
.description-block {
- padding: 0px;
- height: 250px;
- margin-bottom: 60px;
-
- @media (max-width: $tablet) {
- height: auto;
- margin-bottom: 50px;
- }
-
- & .ignite-image {
- padding-right:0;
- top: -115px;
-
- @media (max-width: $tablet) {
- top: auto;
- }
-
- @media (max-width: $mobile) {
- top: auto;
- margin-top: 20px;
- }
- }
- }
-
- .description-block-2 {
padding: 0px;
margin-bottom: 30px;
@@ -1824,6 +1805,11 @@ div.square {
margin-top: 20px;
}
}
+
+ p {
+ font-size: 28px;
+ line-height: 40px;
+ }
}
.img-holder {
@@ -1891,10 +1877,13 @@ div.square {
#whatisignite-feature-desc {
- h3 {
- font-size: 30px;
+ h2 {
+ font-size: 32px;
+ }
- padding-top: 20px;
+ h3 {
+ font-size: 28px;
+ line-height: 40px;
}
p {
Modified: ignite/site/trunk/whatisignite.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1808276&r1=1808275&r2=1808276&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Wed Sep 13 19:28:27 2017
@@ -40,6 +40,7 @@ under the License.
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="0" />
<title>What is Apache Ignite</title>
+ <meta name="description" content="Apache Ignite components and facts: in-memory and persistent modes, distributed SQL database, in-memory data grid, in-memory database, ACID transactions, collocated processing, and more...">
<link media="all" rel="stylesheet" href="/css/all.css?v=1.11">
<link href="https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css" rel="stylesheet">
<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'>
@@ -52,84 +53,140 @@ under the License.
<main id="main" role="main" class="container">
<section id="whatisignite" class="page-section" style="border: none;">
- <h1 class="first heading"><span>What is Ignite?</span></h1>
+ <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">
- <div class="col-sm-6 col-md-6 col-xs-12">
- <ul class="page-list">
- <li><p>the <strong>in-memory</strong> computing platform</p></li>
- <li><p>that is strongly <strong>consistent</strong></p></li>
- <li><p>and highly <strong>available</strong></p></li>
- <li><p>with powerful <strong>SQL</strong>,</p></li>
- <li><p><strong>key-value</strong> and <strong>processing</strong> APIs</p></li>
- </ul>
- </div>
- <div class="col-sm-6 col-md-6 col-xs-12 ignite-image">
- <a href="/images/Main-Ignite-diagram_v2.png"><img class="img-responsive" src="/images/Main-Ignite-diagram_v2.png" width="500px" style="float:right;"/></a>
- </div>
+ <p style="text-align: center;"><i>the <strong>in-memory</strong>Â computing platform<br/>
+ that is <strong>durable</strong>, <strong>strongly consistent</strong>, and <strong>highly available</strong><br/>
+ with powerful <strong>SQL</strong>, <strong>key-value</strong> and <strong>processing</strong> APIs</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/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><strong>in-memory database</strong></i></nobr> or <nobr><i><strong>in-memory data grid</strong></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><strong>horizontally scalable database</strong></i></nobr> that guarantees full data consistency and is
+ resilient to full cluster failures.
+ </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><strong>distributed SQL database</strong></i>.
+ </p>
+
+ <h3>Key-Value</h3>
+ <p>
+ The in-memory data grid component in Ignite is a fully transactional <i><strong>distributed key-value store</strong></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. <i><strong>collocating</strong></i> computations with data. 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">
- <p>Here are some answers to frequently asked questions about Apache Ignite: </p><br/><br/>
- <h2>Is Ignite an in-memory database (IMDB)?</h2>
- <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 pure distributed in-memory database, with strong
- support for SQL and distributed joins.
- </p>
- <p><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql"></a></p><br/><br/>
-
- <h2>Is Ignite an in-memory data grid (IMDG)?</h2>
- <p>
- <strong>Yes</strong>. Ignite is a full-featured data grid, which can be used either in pure
- in-memory mode or with Ignite native persistence. It can also integrate with any 3rd party databases,
- including any RDBMS or NoSQL stores.
- </p>
- <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid"></a></p><br/><br/>
-
- <h2>Is Ignite a distributed database?</h2>
- <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><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql"></a></p><br/><br/>
-
- <h2>Is Ignite an SQL database?</h2>
- <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 broadcast
- message for each update and significantly hurt performance and scalability of the system.
- </p>
- <p><a href="https://apacheignite.readme.io/v2.1/docs/indexes"></a></p><br/><br/>
-
- <h2>Is Ignite a transactional database?</h2>
- <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.3.
- </p>
- <p><a href="https://apacheignite.readme.io/v2.1/docs/sql-queries#known-limitations"></a></p><br/><br/>
-
- <h2>Is Ignite a key-value store?</h2>
- <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/v2.1/docs/data-grid"></a></p><br/><br/>
+ <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 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 pure 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 data grid, which can be used either in pure
+ in-memory mode or with Ignite native persistence. It can also integrate with any 3rd party databases,
+ including any RDBMS or NoSQL stores.
+ </p>
+ <br/><br/>
+
+ <h3>Is Ignite a persistent or pure in-memory storage?</h3>
+ <p>
+ <strong>Both</strong>. Native persistence in Ignite can be turned on and off. This allows Ignite users
+ to store smaller operational data sets in-memory only, and larger data sets on disk, using memory as
+ a caching layer for better performance.
+ </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 broadcast
+ message for each update and significantly hurt performance and scalability of the system.
+ </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.4.
+ </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/>
- <h2>Book</h2>
+ <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>
</main>
@@ -137,4 +194,4 @@ under the License.
</div>
<!--#include virtual="/includes/scripts.html" -->
</body>
-</html>
+</html>
\ No newline at end of file