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 2020/02/03 19:12:50 UTC
svn commit: r1873545 - in /ignite/site/branches/ignite-redisign: ./
features/ includes/ use-cases/ use-cases/database/
Author: dmagda
Date: Mon Feb 3 19:12:50 2020
New Revision: 1873545
URL: http://svn.apache.org/viewvc?rev=1873545&view=rev
Log:
Updated in-memory database page
Added:
ignite/site/branches/ignite-redisign/use-cases/in-memory-database.html
- copied, changed from r1873544, ignite/site/branches/ignite-redisign/use-cases/database/in-memory-database.html
Removed:
ignite/site/branches/ignite-redisign/use-cases/database/distributed-database.html
ignite/site/branches/ignite-redisign/use-cases/database/in-memory-database.html
ignite/site/branches/ignite-redisign/use-cases/database/sql-database.html
Modified:
ignite/site/branches/ignite-redisign/.htaccess
ignite/site/branches/ignite-redisign/features/datagrid.html
ignite/site/branches/ignite-redisign/includes/header.html
ignite/site/branches/ignite-redisign/use-cases/in-memory-cache.html
ignite/site/branches/ignite-redisign/usecases.html
Modified: ignite/site/branches/ignite-redisign/.htaccess
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/.htaccess?rev=1873545&r1=1873544&r2=1873545&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/.htaccess (original)
+++ ignite/site/branches/ignite-redisign/.htaccess Mon Feb 3 19:12:50 2020
@@ -7,14 +7,17 @@ Redirect 301 /features/dotnet.html /feat
Redirect 301 /features/cpp.html /features/multilanguage.html
Redirect 301 /features/clientprotos.html /features/multilanguage.html
Redirect 301 collocatedprocessing.html /features/collocatedprocessing.html
-Redirect 301 /features/durablememory.html /arch/durablememory.html
+Redirect 301 /features/durablememory.html /arch/memorycentric.html
+Redirect 301 /arch/durablememory.html /arch/memorycentric.html
Redirect 301 /memorycentric.html /arch/memorycentric.html
Redirect 301 /features/persistence.html /arch/persistence.html
Redirect 301 /features/deploy.html /arch/clustering.html
Redirect 301 /features/igniterdd.html /use-cases/spark/shared-memory-layer.html
Redirect 301 /use-cases/spark/shared-memory-layer.html /use-cases/spark-acceleration.html
Redirect 301 /use-cases/caching/database-caching.html /use-cases/in-memory-cache.html
-
+Redirect 301 /use-cases/database/in-memory-database.html /use-cases/in-memory-database.html
+Redirect 301 /use-cases/database/distributed-database.html /use-cases/in-memory-database.html
+Redirect 301 /use-cases/database/sql-database.html /use-cases/in-memory-database.html
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
Modified: ignite/site/branches/ignite-redisign/features/datagrid.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/features/datagrid.html?rev=1873545&r1=1873544&r2=1873545&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/features/datagrid.html (original)
+++ ignite/site/branches/ignite-redisign/features/datagrid.html Mon Feb 3 19:12:50 2020
@@ -53,7 +53,7 @@ under the License.
<main id="main" role="main" class="container">
<section id="datagrid" class="page-section">
- <h1 class="first">Key-Value In-Memory Data Grid</h1>
+ <h1 class="first">In-Memory Data Grid With SQL, ACID Transactions and Compute APIs</h1>
<div class="col-sm-12 col-md-12 col-xs-12" style="padding:0 0 20px 0;">
<p>
Apache Ignite provides an extensive set of APIs to act as an in-memory data grid that integrates into
@@ -136,7 +136,7 @@ under the License.
</p>
<p>
<a href="/features/collocatedprocessing.html">
- <b>Co-located processing <i class="fa fa-angle-double-right"></i></b>
+ <b>Co-located Processing <i class="fa fa-angle-double-right"></i></b>
</a>
</p>
<p>
@@ -150,12 +150,17 @@ under the License.
</a>
</p>
<p>
+ <a href="/features/machinelearning.html">
+ <b>Machine and Deep Learning <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
<a href="/arch/persistence.html">
<b>Native Persistence <i class="fa fa-angle-double-right"></i></b>
</a>
</p>
<p>
- <a href="/use-cases/database/in-memory-database.html">
+ <a href="/use-cases/in-memory-database.html">
<b>Ignite as an In-Memory Database <i class="fa fa-angle-double-right"></i></b>
</a>
</p>
Modified: ignite/site/branches/ignite-redisign/includes/header.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/includes/header.html?rev=1873545&r1=1873544&r2=1873545&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/includes/header.html (original)
+++ ignite/site/branches/ignite-redisign/includes/header.html Mon Feb 3 19:12:50 2020
@@ -113,7 +113,7 @@
onclick="ga('send', 'event', 'apache_ignite_usecases', 'menu_click', 'data_grid');">
In-Memory Data Grid</a>
</li>
- <li><a href="/use-cases/database/in-memory-database.html" aria-label="In-Memory Database"
+ <li><a href="/use-cases/in-memory-database.html" aria-label="In-Memory Database"
onclick="ga('send', 'event', 'apache_ignite_usecases', 'menu_click', 'distributed-database');">
In-Memory Database</a>
</li>
Modified: ignite/site/branches/ignite-redisign/use-cases/in-memory-cache.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/use-cases/in-memory-cache.html?rev=1873545&r1=1873544&r2=1873545&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/use-cases/in-memory-cache.html (original)
+++ ignite/site/branches/ignite-redisign/use-cases/in-memory-cache.html Mon Feb 3 19:12:50 2020
@@ -53,7 +53,7 @@ under the License.
<main id="main" role="main" class="container">
<section id="database-caching" class="page-section">
- <h1 class="first">In-Memory Cache With ANSI SQL, ACID Transactions and Compute APIs</h1>
+ <h1 class="first">In-Memory Cache With SQL, ACID Transactions and Compute APIs</h1>
<div class="col-sm-12 col-md-12 col-xs-12" style="padding:0 0 20px 0;">
<div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0;">
<p>
@@ -135,7 +135,7 @@ under the License.
</p>
<p>
<a href="/features/collocatedprocessing.html">
- <b>Co-located processing <i class="fa fa-angle-double-right"></i></b>
+ <b>Co-located Processing <i class="fa fa-angle-double-right"></i></b>
</a>
</p>
<p>
@@ -149,12 +149,17 @@ under the License.
</a>
</p>
<p>
+ <a href="/features/machinelearning.html">
+ <b>Machine and Deep Learning <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
<a href="/features/datagrid.html">
<b>Ignite as an In-Memory Data Grid <i class="fa fa-angle-double-right"></i></b>
</a>
</p>
<p>
- <a href="/use-cases/database/in-memory-database.html">
+ <a href="/use-cases/in-memory-database.html">
<b>Ignite as an In-Memory Database <i class="fa fa-angle-double-right"></i></b>
</a>
</p>
Copied: ignite/site/branches/ignite-redisign/use-cases/in-memory-database.html (from r1873544, ignite/site/branches/ignite-redisign/use-cases/database/in-memory-database.html)
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/use-cases/in-memory-database.html?p2=ignite/site/branches/ignite-redisign/use-cases/in-memory-database.html&p1=ignite/site/branches/ignite-redisign/use-cases/database/in-memory-database.html&r1=1873544&r2=1873545&rev=1873545&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/use-cases/database/in-memory-database.html (original)
+++ ignite/site/branches/ignite-redisign/use-cases/in-memory-database.html Mon Feb 3 19:12:50 2020
@@ -36,7 +36,13 @@ under the License.
<link rel="canonical" href="https://ignite.apache.org/use-cases/database/in-memory-database.html"/>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <meta name="description"
+ content="Apache Ignite, as an In-Memory Database, is a high-performant system-of-records that is capable of
+ storing and querying much larger data sets from disk with no need for memory warm-ups on restarts."/>
+
<title>In-Memory Database - Apache Ignite</title>
+
<!--#include virtual="/includes/styles.html" -->
<!--#include virtual="/includes/sh.html" -->
@@ -47,41 +53,128 @@ under the License.
<main id="main" role="main" class="container">
<section id="key-value-store" class="page-section">
- <h1 class="first">In-Memory Database</h1>
+ <h1 class="first">In-Memory Database With Transactional Persistence</h1>
<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>
- Ignite can be used as a distributed and horizontally scalable
- <code>in-memory database</code> (IMDB) that supports ACID transactions and
- can be used with SQL, key-value, compute, machine learning and other data processing APIs.
- </p>
- <p>
- Ignite memory-centric storage allows to store data and indexes both, in memory and on disk.
- The disk persistence is optional. When persistence is turned on, Ignite can store more data
- than can fit in the available memory, and
- will act as a complete <a href="/use-cases/database/distributed-database.html">distributed SQL database</a>.
+ Apache Ignite, as an in-memory database, is a high-performant system-of-records that is capable
+ of storing and querying much larger data sets from disk with no need for memory warm-ups on
+ restarts.
</p>
<p>
- In scenarios when the whole data set and indexes fit in memory, and the persistence is disabled,
- Ignite will function as an <code>in-memory database</code> supporting SQL, together with
- all the existing APIs for memory-only use cases.
+ That's a distributed database that scales horizontally across memory and disk tiers and supports
+ ACID transactions, ANSI SQL, key-value, compute, machine learning, and other data processing
+ APIs.
</p>
</div>
<div class="col-sm-6 col-md-5 col-xs-12" style="padding-right:0">
<img class="img-responsive" src="/images/sql_database.png" width="400px" style="float:right;"/>
</div>
</div>
+
+ <div class="page-heading">Memory-Centric Architecture</div>
+ <p>
+ Apache Ignite memory management system is memory-centric in the sense that most of the processing takes
+ place in-memory on cached data with a superset of data persisted to disk. Such an architecture lets
+ combine advantages of in-memory computing with the disk durability and strong consistency in one system.
+ </p>
+ <p>
+ When the native persistence is enabled, Ignite allows you to control how much memory space is to be
+ consumed by Ignite. Depending on the memory space available, Ignite either caches a full data set in
+ memory, thus, performing as fast as it can or keeps only the most frequently data there, pulling
+ missing records from disk. For instance, if there are 100 records and your memory capacity allows to
+ cache only 20 of them, then all 100 will be stored on disk, and only 20 will be cached in memory for
+ better performance.
+ </p>
+
+ <p>
+ Overall, these are the primary advantages of Ignite memory-centric architecture:
+ </p>
+ <ul class="page-list" style="margin-bottom: 20px;">
+ <li>
+ Flexible configuration of available memory and disk resources as long as Ignite allows storing a
+ superset of data on disk and only the most frequently used subsets in memory.
+ </li>
+ <li>
+ Ignite SQL queries and all other APIs can query both cached data sets as well as other data that
+ is kept on disk only.
+ </li>
+ <li>
+ Instantaneous cluster restarts. Ignite becomes fully operational from disk immediately upon cluster
+ startup or restarts. There is no need to preload or warm up the in-memory caches.
+ </li>
+ </ul>
+
+ <div class="page-heading">Better High-Availability With Instantaneous Cluster Restarts</div>
+
+ <p>
+ If you enable Ignite native persistence for your deployments, then there is no need to worry about
+ time-consuming memory warm-ups on cluster restarts. As long as Ignite persistence always keeps a
+ superset of data on disk and treats it as one of the storage layers, Ignite starts reading data from
+ the persistence as soon as the cluster becomes active. The memory tier is warmed up in the background
+ with the data Ignite accesses on disk for you.
+ </p>
+
+ <div class="page-heading">Avoiding Network Impact on Performance With Co-located Processing</div>
+
+ <p>
+ The disk-centric systems, like RDBMS or NoSQL, generally utilize the classic client-server approach,
+ when the data is transferred from the server to the client-side where it gets processed and then usually
+ discarded. This approach does not scale well as moving the data over the network is the most expensive
+ operation in a distributed system.
+ </p>
+ <p>
+ Many distributed databases, including Apache Ignite, support another more scalable approach called
+ co-located processing that eliminates or reduces network traffic significantly by running application
+ logic right on the cluster nodes. This approach executes data or compute-intensive logic, including
+ distributed SQL with JOINs, exactly where the data resides, thus, reducing data shuffling over the network.
+ </p>
+
+ <div class="page-heading">Learn More</div>
+ <p>
+ <a href="/arch/memorycentric.html">
+ <b>Memory-Centric Storage <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
+ <a href="/arch/persistence.html">
+ <b>Native Persistence <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
+ <a href="/features/collocatedprocessing.html">
+ <b>Co-located Processing <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
+ <a href="/features/sql.html">
+ <b>Distributed SQL <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
+ <a href="/features/transactions.html">
+ <b>ACID Transactions <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
+ <a href="/features/machinelearning.html">
+ <b>Machine and Deep Learning <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
+ <p>
+ <a href="/features/datagrid.html">
+ <b>Ignite as an In-Memory Data Grid <i class="fa fa-angle-double-right"></i></b>
+ </a>
+ </p>
<p>
- One of the distinguishing characteristics of Ignite SQL is the support for
- <nobr><a href="https://apacheignite-sql.readme.io/docs/distributed-joins" target="_blank" rel="noopener">distributed SQL JOINs</a></nobr>,
- which works in both, collocated and non-collocated fashions. When collocated, the JOINs are
- executed on the local data available on each node without having to move large data sets
- across the network. Such collocated approach provides the best scalability and performance
- in distributed clusters.
+ <a href="/use-cases/in-memory-cache.html">
+ <b>Ignite as an In-Memory Cache <i class="fa fa-angle-double-right"></i></b>
+ </a>
</p>
<p>
- You should also check Ignite <a href="/features/sql.html">distributed SQL</a> and
- <a href="/features/datagrid.html" class="text-nowrap">data grid</a> features.
+ <a href="TODO">
+ <b>Ignite as a Digital Integration Hub <i class="fa fa-angle-double-right"></i></b>
+ </a>
</p>
</section>
</main>
Modified: ignite/site/branches/ignite-redisign/usecases.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/usecases.html?rev=1873545&r1=1873544&r2=1873545&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/usecases.html (original)
+++ ignite/site/branches/ignite-redisign/usecases.html Mon Feb 3 19:12:50 2020
@@ -64,7 +64,6 @@ under the License.
onclick="ga('send', 'event', 'apache_ignite_usecases', 'usecases_page_click', 'distributed-database');">
In-Memory Database</a>
</li>
- <!--<li><a href="/use-cases/database/sql-database.html">SQL Database</a></li>-->
<li><a href="/features/datagrid.html" aria-label="In-Memory Data Grid"
onclick="ga('send', 'event', 'apache_ignite_usecases', 'usecases_page_click', 'data_grid');">
In-Memory Data Grid</a>