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/03/11 22:11:46 UTC
svn commit: r1875105 [1/7] - in /ignite/site/branches/ignite-redisign: ./
arch/ community/ css/ features/ scss/ use-cases/
Author: dmagda
Date: Wed Mar 11 22:11:46 2020
New Revision: 1875105
URL: http://svn.apache.org/viewvc?rev=1875105&view=rev
Log:
merged Mauricio's changes
Modified:
ignite/site/branches/ignite-redisign/arch/clustering.html
ignite/site/branches/ignite-redisign/arch/multi-tier-storage.html
ignite/site/branches/ignite-redisign/arch/persistence.html
ignite/site/branches/ignite-redisign/community/contribute.html
ignite/site/branches/ignite-redisign/community/resources.html
ignite/site/branches/ignite-redisign/css/ignite-redesign.css
ignite/site/branches/ignite-redisign/docs-and-apis.html
ignite/site/branches/ignite-redisign/events.html
ignite/site/branches/ignite-redisign/features.html
ignite/site/branches/ignite-redisign/features/collocatedprocessing.html
ignite/site/branches/ignite-redisign/features/computegrid.html
ignite/site/branches/ignite-redisign/features/datastructures.html
ignite/site/branches/ignite-redisign/features/machinelearning.html
ignite/site/branches/ignite-redisign/features/manageandmonitor.html
ignite/site/branches/ignite-redisign/features/messaging.html
ignite/site/branches/ignite-redisign/features/multilanguage.html
ignite/site/branches/ignite-redisign/features/rdbmsintegration.html
ignite/site/branches/ignite-redisign/features/servicegrid.html
ignite/site/branches/ignite-redisign/features/sql.html
ignite/site/branches/ignite-redisign/features/streaming.html
ignite/site/branches/ignite-redisign/features/tensorflow.html
ignite/site/branches/ignite-redisign/features/transactions.html
ignite/site/branches/ignite-redisign/meetup-groups.html
ignite/site/branches/ignite-redisign/package-lock.json
ignite/site/branches/ignite-redisign/screencasts.html
ignite/site/branches/ignite-redisign/scss/ignite-redesign.scss
ignite/site/branches/ignite-redisign/use-cases/datagrid.html
ignite/site/branches/ignite-redisign/use-cases/dih.html
ignite/site/branches/ignite-redisign/use-cases/hadoop-acceleration.html
ignite/site/branches/ignite-redisign/use-cases/hpc.html
ignite/site/branches/ignite-redisign/use-cases/in-memory-cache.html
ignite/site/branches/ignite-redisign/use-cases/in-memory-database.html
ignite/site/branches/ignite-redisign/use-cases/key-value-store.html
ignite/site/branches/ignite-redisign/use-cases/provenusecases.html
ignite/site/branches/ignite-redisign/use-cases/spark-acceleration.html
ignite/site/branches/ignite-redisign/whatisignite.html
Modified: ignite/site/branches/ignite-redisign/arch/clustering.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/arch/clustering.html?rev=1875105&r1=1875104&r2=1875105&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/arch/clustering.html (original)
+++ ignite/site/branches/ignite-redisign/arch/clustering.html Wed Mar 11 22:11:46 2020
@@ -52,87 +52,80 @@ under the License.
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
- <!--#include virtual="/includes/header.html" -->
- <main id="main" role="main" class="container">
- <section id="deployment-options" class="page-section">
- <h1 class="first">Deploy Anywhere</h1>
- <div class="col-sm-12 col-md-12 col-xs-12" style="padding-left:0; padding-right:0;">
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0;">
- <p>
- Apache Ignite implements the shared-nothing architecture where all cluster nodes are equal
- and there is no single point of failure or bottleneck.
- Ignite does NOT have a component such as a master node or name node that is present in most
- distributed systems.
- </p>
- <p>
- Ignite nodes discover each other automatically in your environment, and the cluster can be
- scaled out or in easily.
- </p>
- <p>
- Apache Ignite can run on bare metal, virtual machines, Docker, Kubernetes, and cloud
- environments. Technically there are no limitations in regards to deployment environments --
- since Ignite nodes can auto-discover each other via the TCP/IP interface, you can launch a
- cluster anywhere.
- </p>
- </div>
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0;">
- <img class="img-responsive" src="/images/ignite-deploy.png" width="540px" style="float:right;"/>
- </div>
- </div>
-
- <div class="page-heading">Servers, Clients and Protocols</div>
- <p>
- Ignite defines two types of nodes â servers and clients.
+ <!--#include virtual="/includes/header.html" -->
+<article>
+ <div class="container">
+ <h1>Deploy <strong>Anywhere</strong></h1>
+
+ <img class="img-responsive diagram-right" src="/images/ignite-deploy.png" />
+ <p>
+ Apache Ignite implements the shared-nothing architecture where all cluster nodes are equal
+ and there is no single point of failure or bottleneck.
+ Ignite does NOT have a component such as a master node or name node that is present in most
+ distributed systems.
+ </p>
+ <p>
+ Ignite nodes discover each other automatically in your environment, and the cluster can be
+ scaled out or in easily.
+ </p>
+ <p>
+ Apache Ignite can run on bare metal, virtual machines, Docker, Kubernetes, and cloud
+ environments. Technically there are no limitations in regards to deployment environments --
+ since Ignite nodes can auto-discover each other via the TCP/IP interface, you can launch a
+ cluster anywhere.
+ </p>
+
- A server node is the base computational and data storage unit. Typically, you start a single server
- node per machine or container and it will scale vertically by utilizing all of the CPU, RAM, and other
- resources available unless specified differently. These resources are pooled and become available to
- Ignite applications once the server node joins the cluster of other server nodes.
- </p>
- <p>
- A cluster is a group of server nodes interconnected together in order to provide shared resources
- like RAM and CPU to your applications.
- </p>
- <p>
- Client nodes (aka. thick clients) are your connection endpoints and gateways from the application layer
- to the cluster of server nodes. You always embed a client into your application code and execute the
- required APIs. The clients shield all the complexity of Igniteâs distributed nature from application
- developers who will see the cluster as a single unit. Itâs as simple as connecting to an RDBMS via a
- JDBC driver or Spring Data framework.
- </p>
- <p>
- In addition to the thick clients, you can access the cluster with Ignite thin clients,
- JDBC and ODBC drivers, or the REST API.
- </p>
+ <h2>Servers, Clients and Protocols</h2>
+ <p>
+ Ignite defines two types of nodes â servers and clients.
- <div class="page-heading">Learn More</div>
- <p>
- <a href="https://apacheignite.readme.io/docs/clustering" target="docs">
- <b>Ignite Clustering <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- <p>
- <a href="https://apacheignite.readme.io/docs/tcpip-discovery" target="docs">
- <b>Discovery SPI Configuration <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- <p>
- <a href="https://apacheignite.readme.io/docs/network-config" target="docs">
- <b>Communication SPI Configuration <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- <p>
- <a href="/features/multilanguage.html">
- <b>Multi-Language Support <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- </section>
- </main>
+ A server node is the base computational and data storage unit. Typically, you start a single server
+ node per machine or container and it will scale vertically by utilizing all of the CPU, RAM, and other
+ resources available unless specified differently. These resources are pooled and become available to
+ Ignite applications once the server node joins the cluster of other server nodes.
+ </p>
+ <p>
+ A cluster is a group of server nodes interconnected together in order to provide shared resources
+ like RAM and CPU to your applications.
+ </p>
+ <p>
+ Client nodes (aka. thick clients) are your connection endpoints and gateways from the application layer
+ to the cluster of server nodes. You always embed a client into your application code and execute the
+ required APIs. The clients shield all the complexity of Igniteâs distributed nature from application
+ developers who will see the cluster as a single unit. Itâs as simple as connecting to an RDBMS via a
+ JDBC driver or Spring Data framework.
+ </p>
+ <p>
+ In addition to the thick clients, you can access the cluster with Ignite thin clients,
+ JDBC and ODBC drivers, or the REST API.
+ </p>
- <!--#include virtual="/includes/footer.html" -->
+ <div class="jumbotron jumbotron-fluid">
+ <div class="container">
+ <div class="title display-6">Learn More</div>
+ <hr class="my-4">
+ <div class="row">
+ <div class="col-6 col-xs-12">
+ <ul>
+ <li><a href="https://apacheignite.readme.io/docs/clustering" target="docs"><b>Ignite Clustering <i class="fa fa-angle-double-right"></i></b></a></li>
+ <li><a href="https://apacheignite.readme.io/docs/tcpip-discovery" target="docs"><b>Discovery SPI Configuration <i class="fa fa-angle-double-right"></i></b></a></li>
+ </ul>
+ </div>
+ <div class="col-6 col-xs-12">
+ <ul>
+ <li><a href="https://apacheignite.readme.io/docs/network-config" target="docs"><b>Communication SPI Configuration <i class="fa fa-angle-double-right"></i></b></a></li>
+ <li><a href="/features/multilanguage.html"><b>Multi-Language Support <i class="fa fa-angle-double-right"></i></b></a></li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div>
</div>
+</article>
+ <!--#include virtual="/includes/footer.html" -->
+
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/branches/ignite-redisign/arch/multi-tier-storage.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/arch/multi-tier-storage.html?rev=1875105&r1=1875104&r2=1875105&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/arch/multi-tier-storage.html (original)
+++ ignite/site/branches/ignite-redisign/arch/multi-tier-storage.html Wed Mar 11 22:11:46 2020
@@ -33,202 +33,141 @@ under the License.
<!DOCTYPE html>
<html lang="en">
<head>
- <link rel="canonical" href="https://ignite.apache.org/arch/multi-tier-storage.html"/>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
- <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"/>
- <meta http-equiv="Pragma" content="no-cache"/>
- <meta http-equiv="Expires" content="0"/>
+<link rel="canonical" href="https://ignite.apache.org/arch/multi-tier-storage.html"/>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"/>
+<meta http-equiv="Pragma" content="no-cache"/>
+<meta http-equiv="Expires" content="0"/>
+<title>Multi-Tier Storage - Apache Ignite</title>
+<meta name="description"
+ content="Apache Ignite multi-tier storage uses memory, disk and Intel® Optane⢠as active storage tiers. Speed of
+ memory with the consistency of disk-based databases and no need for memory warm-ups on restarts."/>
- <title>Multi-Tier Storage - Apache Ignite</title>
+<!--#include virtual="/includes/styles.html" -->
- <meta name="description"
- content="Apache Ignite multi-tier storage uses memory, disk, and Intel® Optane⢠as active storage tiers to
- provide the speed of memory with the consistency of disk-based databases without the need for memory
- warm-ups on restarts."/>
-
- <!--#include virtual="/includes/styles.html" -->
-
- <!--#include virtual="/includes/sh.html" -->
+<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
- <!--#include virtual="/includes/header.html" -->
-
- <main id="main" role="main" class="container">
- <section id="multi-tier" class="page-section">
- <h1 class="first">Multi-Tier Storage</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; padding-right:0">
- <p>
- Apache Ignite is designed to work with memory, disk, and Intel® Optane⢠as active storage tiers.
- The memory tier allows using DRAM and Intel® Optane⢠operating in the Memory Mode for data storage
- and processing needs. The disk tier is optional with the support of two options -- you can
- persist data in an external database or keep it in the Ignite native persistence. SSD, Flash,
- HDD, or Intel® Optane⢠operating in the AppDirect Mode can be used as a storage device.
- </p>
- </div>
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0">
- <img class="img-responsive" src="/images/durable_memory.png" width="440px" style="float: right;"/>
- </div>
- </div>
- <p>
- Ignite takes full control of its memory tier by allocating and managing off-heap regions. Each Ignite
- server node allocates memory regions during bootstrap, splits the regions into pages, and keeps data
- records with indexes in those pages. Java heap is used to keep temporary objects such as query result
- sets, metrics samples, and objects generated by your application code. All these objects are garbage
- collected eventually.
- </p>
- <p>
- If you select the native persistence as the disk tier, then most of the processing will still take place
- in memory on cached data, but, with a full copy stored on disk. If any record is missing in memory,
- Ignite will read it from disk, allowing you to persist much larger data sets than you can cache in memory.
- This also eliminates the need for time-consuming memory warm-ups on restarts. As soon as your cluster
- reconnects after a restart, Ignite will serve most of the data from disk warming up the memory tier in
- the background.
- </p>
-
- <div class="page-heading" id="storage-usage-modes">
- Multi-Tier Storage Usage Modes
- <a href="/arch/multi-tier-storage.html#storage-usage-modes"><i class="fa fa-anchor"></i></a>
+<!--#include virtual="/includes/header.html" -->
+<article>
+ <div class="container">
+
+ <h1>Multi-Tier <strong>Storage</strong></h1>
+
+ <p> Apache Ignite is designed to work with memory, disk and Intel® Optane⢠as active storage tiers.
+ The memory tier allows to use DRAM and Intel® Optane⢠operating in the Memory Mode for data storage and processing needs.
+ The disk tier is optional with the support of two options -- you can persist data in an external database or keep it in the Ignite native persistence. SSD, Flash, HDD or Intel® Optane⢠operating in the AppDirect Mode can be used as a storage device. </p>
+ <img class="img-fluid diagram-right" src="/images/durable_memory.png" />
+
+ <p> Ignite takes full control of its memory tier by allocating and managing off-heap regions. Each Ignite
+ server node allocates memory regions during bootstrap, splits the regions into pages, and keeps data
+ records with indexes there. Java heap is used to keep temporary objects such as queries results sets,
+ metrics samples, objects generated by your application code. All these objects are garbage collected
+ eventually. </p>
+ <p> If you select the native persistence as the disk tier, then most of the processing will still
+ take place in memory on cached data, but, with a full copy stored on disk. If any record is
+ missing in memory, Ignite will read it from disk, allowing you to persist much larger data sets
+ than you can cache in memory. That also eliminates the need for time-consuming memory warm-ups
+ on restarts. As soon as your cluster reconnects after a restart, Ignite will serve most of the
+ data from disk warming the memory tier up in the background. </p>
+
+ <h2>Multi-Tier Storage Usage Modes <a href="/arch/multi-tier-storage.html#storage-usage-modes"><i class="fa fa-anchor"></i></a> </h2>
+
+ <p>Below you can see primary modes for multi-tier storage usage and configuration:</p>
+
+ <table class="table table-bordered table-striped" name="Deployment Options Features">
+ <thead>
+ <tr>
+ <th width="35%" class="left">Mode</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="left">In-Memory</td>
+ <td><p> The whole data set is available in memory only. In order to survive node failures, it is
+ recommended to keep at least one backup copy of the data across the cluster. DRAM or Intel®
+ Optane⢠operating in the Memory Mode can be used as a storage device. </p>
+ <p> <strong>Use cases</strong>: general in-memory caching, high-performance
+ computing, web-session caching, real-time processing of continuous data streams. </p></td>
+ </tr>
+ <tr>
+ <td class="left">In-Memory + External Database</td>
+ <td><p> Ignite is deployed as a distributed caching layer on top of an existing external database.
+ This mode is for the acceleration of disk-based databases and your services with APIs that
+ interact with them. </p>
+ <p> <strong>Use cases</strong>: acceleration of services and APIs with write-through/behind
+ capability, to an external database (aka. in-memory data grid). </p></td>
+ </tr>
+ <tr>
+ <td class="left">In-Memory Cache + Native Persistence</td>
+ <td><p> 100% of data is persisted to disk, and the same or smaller amount is cached in memory.
+ The more data is cached, the faster is the performance. The disk serves as the primary
+ storage that survives any cluster failures and restarts. No need for memory warm-ups on
+ restarts as long as Ignite can serve data from disk. SSD, Flash, HDD or Intel®
+ Optane⢠operating in the AppDirect Mode can be used as a storage device. </p>
+ <p> <strong>Use cases</strong>: Ignite as an in-memory database or digital integration hub
+ with the active persistence layer. </p></td>
+ </tr>
+ </tbody>
+ </table>
+
+
+ <h2>Partitioning & Replication <a href="/arch/multi-tier-storage.html#partitioning"><i class="fa fa-anchor"></i></a> </h2>
+ <p>Depending on the configuration, Ignite can both partition or replicate data across the cluster. With the replicated mode, each cluster node keeps a full copy of the data that is advantageous for frequently accessed dictionaries. As for the partitioned mode, Ignite spreads the data across all the cluster nodes evenly, allowing to store much more than a single machine can fit in.</p>
+
+ <h2>Durability and Consistency <a href="/arch/multi-tier-storage.html#durability"><i class="fa fa-anchor"></i></a> </h2>
+ <p>Ignite provides strong ACID durability guarantees to the data:</p>
+ <ul class="page-list" style="margin-bottom: 20px;">
+ <li>Committed transactions always survive failures.</li>
+ <li>The cluster can always be recovered to the latest successfully committed transaction.</li>
+ </ul>
+
+
+ <h2>Write-Ahead Logging and Checkpointing <a href="/arch/multi-tier-storage.html#write-ahead-log"><i class="fa fa-anchor"></i></a></h2>
+ <p> If Ignite native persistence is selected as a disk tier, then every time a record is updated in memory, the change is added to the write-ahead log (WAL). The purpose of the WAL is to propagate updates to disk in the fastest way possible and provide a consistent recovery mechanism that supports full cluster failures. </p>
+ <p> As WAL grows, it periodically gets checkpointed to the main storage. Checkpointing is the process of copying dirty pages from the memory tier to the partition files on disk. A dirty page is a page that was updated in memory, was appended to WAL, but was not written to a respective partition file on disk yet. </p>
+
+
+ <div class="jumbotron jumbotron-fluid">
+ <div class="container">
+ <div class="display-6 title">Learn More</div>
+ <hr class="my-4">
+ <div class="row">
+ <div class="col-6 col-xs-12">
+ <ul>
+ <li>
+ <p><a href="https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood" target="docs">Multi-Tier Storage Implementation Details <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="/arch/persistence.html"> Native Persistence <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="/features/datagrid.html"> Ignite as an In-Memory Data Grid <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ </ul>
+ </div>
+ <div class="col-6 col-xs-12">
+ <ul>
+ <li>
+ <p><a href="/use-cases/in-memory-database.html"> Ignite as an In-Memory Database <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="/use-cases/dih.html"> Ignite as a Digital Integration Hub <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="/use-cases/hpc.html"> Ignite for High Performance Computing <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ </ul>
+ </div>
</div>
- <table class="formatted" name="Deployment Options Features">
- <thead>
- <tr>
- <th width="35%" class="left">Mode</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="left">In-Memory</td>
- <td>
- <p>
- The whole data set is available in memory only. In order to survive node failures, we
- recommend keeping at least one backup copy of the data across the cluster. DRAM or
- Intel® Optane⢠operating in the Memory Mode can be used as a storage device.
- </p>
-
- <p>
- <strong>Use cases</strong>: general in-memory caching, high-performance
- computing, web-session caching, real-time processing of continuous data streams.
- </p>
- </td>
- </tr>
- <tr>
- <td class="left">In-Memory + External Database</td>
- <td>
- <p>
- Ignite is deployed as a distributed caching layer on top of an existing external database.
- This mode is for accelerating disk-based databases and your services with APIs that
- interact with them.
- </p>
-
- <p>
- <strong>Use cases</strong>: acceleration of services and APIs with write-through and
- write-behind capability, to an external database.
- </p>
- </td>
- </tr>
- <tr>
- <td class="left">In-Memory Cache + Native Persistence</td>
- <td>
- <p>
- 100% of data is persisted to disk, and the same or smaller amount is cached in memory. The
- more data is cached, the faster is the performance. The disk serves as the primary storage
- that survives any cluster failures and restarts. There is no need for memory warm-ups on
- restarts since Ignite can serve data from disk. SSD, Flash, HDD or Intel® Optane⢠operating
- in the AppDirect Mode can be used as a storage device.
- </p>
-
- <p>
- <strong>Use cases</strong>: Ignite as an in-memory database or digital integration hub
- with the active persistence layer.
- </p>
- </td>
- </tr>
- </tbody>
- </table>
-
- <h2 style="padding-top: 10px;" id="partitioning">
- Partitioning & Replication
- <a href="/arch/multi-tier-storage.html#partitioning"><i class="fa fa-anchor"></i></a>
- </h2>
- <p>
- Depending on the configuration, Ignite can both partition or replicate data across the cluster. In the
- replicated mode, each cluster node keeps a full copy of the data, but the size of a replicated cache is
- limited by the amount of memory available on the node. In the partitioned mode, Ignite spreads the data
- across all the cluster nodes evenly, allowing you to store much more than what can fit in a single machine.
- </p>
-
- <h2 style="padding-top: 10px;" id="durability">
- Durability and Consistency
- <a href="/arch/multi-tier-storage.html#durability"><i class="fa fa-anchor"></i></a>
- </h2>
- <p>
- Ignite provides the following ACID guarantees across the cluster:
- </p>
-
- <ul class="page-list" style="margin-bottom: 20px;">
- <li>Committed transactions always survive failures.</li>
- <li>
- The cluster can always be recovered to the latest successfully committed transaction.
- </li>
- </ul>
-
-
- <h2 style="padding-top: 10px;" id="write-ahead-log">
- Write-Ahead Logging and Checkpointing
- <a href="/arch/multi-tier-storage.html#write-ahead-log"><i class="fa fa-anchor"></i></a>
- </h2>
- <p>
- If Ignite native persistence is selected as a disk tier, then every time a record is updated in memory,
- the change is added to the write-ahead log (WAL). The purpose of the WAL is to propagate updates to disk
- in the fastest way possible and provide a consistent recovery mechanism that supports full cluster failures.
- </p>
-
- <p>
- As WAL grows, it periodically gets checkpointed to the main storage. Checkpointing is the process of
- copying dirty pages from the memory tier to the partition files on disk. A dirty page is a page that was
- updated in memory, was appended to WAL, but was not written to the respective partition file on disk yet.
- </p>
-
- <div class="page-heading">Learn More</div>
- <p>
- <a href="https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood" target="docs">
- <b>Multi-Tier Storage Implementation Details <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/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/in-memory-database.html">
- <b>Ignite as an In-Memory Database <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- <p>
- <a href="/use-cases/dih.html">
- <b>Ignite as a Digital Integration Hub <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- <p>
- <a href="/use-cases/hpc.html">
- <b>Ignite for High Performance Computing <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- </section>
- </main>
-
- <!--#include virtual="/includes/footer.html" -->
-</div>
+ </div>
+ </div>
+
+ </div>
+ </article>
+<!--#include virtual="/includes/footer.html" -->
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/branches/ignite-redisign/arch/persistence.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/arch/persistence.html?rev=1875105&r1=1875104&r2=1875105&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/arch/persistence.html (original)
+++ ignite/site/branches/ignite-redisign/arch/persistence.html Wed Mar 11 22:11:46 2020
@@ -51,119 +51,111 @@ under the License.
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
<!--#include virtual="/includes/header.html" -->
+ <article>
+ <div class="container">
+ <h1>Apache Ignite <strong>Native Persistence</strong></h1>
+ <p>
+ Even though Apache Ignite is broadly used as a caching layer on top of external databases, it
+ comes with its native persistence that is a distributed, ACID, and SQL-compliant disk-based
+ store.
+ The native persistence integrates into the Ignite multi-tier storage as a disk tier that can
+ be turned on to let Ignite store more data on disk than it can cache in memory and to enable
+ fast cluster restarts.
+ </p>
+ <p>
+ With native persistence enabled, Ignite always stores a superset of data on disk, and caches as
+ much as
+ it can in memory. For example, if your application stores 200 records in an Ignite cluster and
+ your
+ memory capacity allows caching only 150 of them, then those 150 records will be served from
+ memory while
+ the rest 50 from disk whenever the application requests them.
+ </p>
+ <a href="/images/native_persistence.png"><img class="img-responsive diagram-right" src="/images/native_persistence.png" alt="Apache Ignite Native Persistence"/></a>
+
+
+ <h2>Ignite Persistence vs. External Databases</h2>
+ <p>
+ The native persistence has the following advantages over external databases that can also be used as
+ the disk tier in Ignite:
+ </p>
+ <ul class="page-list" >
+ <li>
+ An ability to cache a subset of the data - the native persistence always stores 100% of data on
+ disk and lets you cache as much as required in memory.
+ </li>
+ <li>
+ An ability to query data from disk - if any record is missing in memory, then Ignite takes it from
+ disk. This is supported for all the APIs including SQL.
+ </li>
+ <li>
+ Instantaneous cluster restarts - Ignite becomes fully operational from disk upon a cluster
+ startup or restarts without requiring to preload or warm up the memory tier.
+ </li>
+ </ul>
+
+ <h2>Write-Ahead Logging and Checkpointing</h2>
+ <p>
+ If Ignite native persistence is selected as a disk tier, then every time a record is updated in memory, the change is added to the write-ahead log (WAL). The purpose of the WAL is to propagate updates to disk in the fastest way possible and provide a consistent recovery mechanism that supports full cluster failures.</p>
+
+ <p>As WAL grows, it periodically gets checkpointed to the main storage. Checkpointing is the process of copying dirty pages from the memory tier to the partition files on disk. A dirty page is a page that was updated in memory, was appended to WAL, but was not written to a respective partition file on disk yet.
+ </p>
+
- <main id="main" role="main" class="container">
- <section id="native-persistence" class="page-section">
- <h1 class="first">Apache Ignite Native Persistence</h1>
- <div class="col-sm-12 col-md-12 col-xs-12" style="padding-left:0; padding-right:0;">
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0;">
- <p>
- Even though Apache Ignite is broadly used as a caching layer on top of external databases, it
- comes with its native persistence - a distributed, ACID, and SQL-compliant disk-based
- store. The native persistence integrates into the Ignite multi-tier storage as a disk tier that
- can be turned on to let Ignite store more data on disk than it can cache in memory and to enable
- fast cluster restarts.
- </p>
- <p>
- With native persistence enabled, Ignite always stores a superset of data on disk, and caches as
- much as it can in memory. For example, if your application needs to store 200 records in an
- Ignite cluster and the memory capacity allows caching only 150 records, then all 200 will be
- stored on disk, out of which 150 will be served from memory while the rest 50 from disk whenever
- the application requests them.
- </p>
- </div>
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0; top: -10px;">
- <a href="/images/native_persistence.png">
- <img class="img-responsive" src="/images/native_persistence.png" width="450px" style="float:right;"
- alt="Apache Ignite Native Persistence"/></a>
- </div>
- </div>
-
- <div class="page-heading">Ignite Persistence vs. External Databases</div>
+ <h2>Durability</h2>
<p>
- The native persistence has the following advantages over external databases:
+ Ignite provides strong ACID durability guarantees to the data:
</p>
- <ul class="page-list" style="margin-bottom: 20px;">
+
+ <ul class="page-list" >
<li>
- The ability to cache a subset of the data - the native persistence always stores 100% of data on
- disk and lets you cache as much as required in memory.
+ Committed transactions always survive failures.
</li>
<li>
- The ability to query data from disk - if any record is missing in memory, then Ignite reads it from
- disk. This is supported for all the APIs including SQL.
+ The cluster can always be recovered to the latest successfully committed transaction.
</li>
+ </ul>
+
+ <div class="jumbotron jumbotron-fluid">
+ <div class="container">
+ <div class="display-6 title">Learn More</div>
+ <hr class="my-4">
+ <div class="row">
+ <div class="col-6 col-xs-12">
+ <ul>
<li>
+ <p><a href="/arch/multi-tier-storage.html">Multi-Tier Storage <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
<li>
- Instantaneous cluster restarts - Ignite becomes fully operational from disk upon a cluster
- startup or restarts without requiring to preload or warm up the memory tier.
+ <p><a href="https://apacheignite.readme.io/docs/distributed-persistent-store" target="docs">Native Persistence Usage and Configuration <i class="fa fa-angle-double-right"></i></a></p>
</li>
- </ul>
-
- <div class="page-heading">Write-Ahead Logging and Checkpointing</div>
- <p>
- If Ignite native persistence is selected as a disk tier, then every time a record is updated in memory,
- the change is added to the write-ahead log (WAL). The purpose of the WAL is to propagate updates to disk
- in the fastest way possible and provide a consistent recovery mechanism that supports full cluster
- failures.
-
- As WAL grows, it periodically gets checkpointed to the main storage. Checkpointing is the process of
- copying dirty pages from the memory tier to the partition files on disk. A dirty page is a page that was
- updated in memory, was appended to WAL, but was not written to the respective partition file on disk yet.
- </p>
-
- <div class="page-heading">Durability</div>
- <p>
- Ignite native persistence provides the following ACID guarantees across the cluster:
- </p>
-
- <ul class="page-list" style="margin-bottom: 20px;">
<li>
- Committed transactions always survive failures.
+ <p><a href="https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood" target="docs">Native Persistence Implementation Details <i class="fa fa-angle-double-right"></i></a></p>
</li>
+ </ul>
+ </div>
+ <div class="col-6 col-xs-12">
+ <ul>
<li>
- The cluster can always be recovered to the latest successfully committed transaction.
+ <p><a href="/features/sql.html">Distributed SQL <i class="fa fa-angle-double-right"></i></a></p>
</li>
- </ul>
-
- <div class="page-heading">Learn More</div>
- <p>
- <a href="/arch/multi-tier-storage.html">
- <b>Multi-Tier Storage <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- <p>
- <a href="https://apacheignite.readme.io/docs/distributed-persistent-store" target="docs">
- <b>Native Persistence Usage and Configuration <i class="fa fa-angle-double-right"></i></b>
- </a>
- </p>
- <p>
- <a href="https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood" target="docs">
- <b>Native Persistence Implementation Details <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/collocatedprocessing.html">
- <b>Co-located Processing <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>
- </section>
-
- </main>
-
- <!--#include virtual="/includes/footer.html" -->
-</div>
+ <li>
+ <p><a href="/features/collocatedprocessing.html">Co-located Processing <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="/features/transactions.html">ACID Transactions <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div>
+
+
+ </div><!-- end .container -->
+</article>
+<!--#include virtual="/includes/footer.html" -->
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/branches/ignite-redisign/community/contribute.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/community/contribute.html?rev=1875105&r1=1875104&r2=1875105&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/community/contribute.html (original)
+++ ignite/site/branches/ignite-redisign/community/contribute.html Wed Mar 11 22:11:46 2020
@@ -45,13 +45,12 @@ under the License.
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
<!--#include virtual="/includes/header.html" -->
-
- <main id="main" role="main" class="container">
- <section id="contribute" class="page-section">
- <h1 class="first">Contribute to Apache Ignite</h1>
- <p>
+<article>
+ <div class="container">
+ <h1 >Contribute to <strong>Apache Ignite</strong></h1>
+
+ <p>
This guide discusses various types of contribution to Apache Ignite extending generic ideas
of the <a href="https://community.apache.org/gettingStarted/101.html" target="_blank">ASF Getting
Started</a>. Contributing to Ignite doesnât just mean writing code. Helping new users on the mailing
@@ -68,9 +67,9 @@ under the License.
<a href="http://www.apache.org/theapacheway/index.html" target="_blank">The Apache Way</a> that helps
us, as a group of professionals, drive the project forward in a respectful and inclusive way.
</p>
-
- <h2>Getting Started</h2>
- <p>
+
+ <h2>Getting Started</h2>
+ <p>
The first thing to do is to sign up to the <a href="mailto:dev@ignite.apache.org">dev mailing
list</a> and say "Hello" to everyone in the community. Tell us as much as you can about your areas of
expertise mentioning how exactly you would like to contribute. We are a friendly and inclusive
@@ -86,8 +85,8 @@ under the License.
How to Collaborate</a> page for more details on various communication channels used by the community
members. Even though most of the discussions take place on the dev list, we hang out in Slack.
</p>
-
- <h2>Contribute by Helping Others</h2>
+
+ <h2>Contribute by Helping Others</h2>
<p>
A great way to contribute to Ignite and to get more practical experience is to help answer
@@ -114,10 +113,8 @@ under the License.
produce and maintain the documentation pages or API references, edit and correct existing content, stay
active on the user and dev mailing lists, and you'll become a committer inevitably.
</p>
- <p>
-
- </p>
- <ul class="page-list">
+
+ <ul class="page-list">
<li>
Come across a misprint or unclear documentation section? Use "Suggest Edits" feature of
our <a href="https://apacheignite.readme.io/docs" target="_blank"> main documentation portal</a> to propose a
@@ -133,8 +130,9 @@ under the License.
pull-request.
</li>
</ul>
-
- <h2>Code Contributions</h2>
+
+
+ <h2>Code Contributions</h2>
<p>
Before you start with code contributions, get to know our
<a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute" target="_blank">Contribution and
@@ -167,8 +165,8 @@ under the License.
target="_blank">All other</a> integrations.
</li>
</ul>
-
- <div class="page-heading">Contribute to Ignite core</div>
+
+ <h2>Contribute to Ignite core</h2>
<p>
If you are willing to contribute to the core components of Ignite then consider one of the tickets
below. Those are the tickets of easy and moderate complexity community members prepared for you to
@@ -207,8 +205,9 @@ under the License.
<a href="https://issues.apache.org/jira/browse/IGNITE/">Ignite Jira</a>, check the latest Ignite
discussions on the dev list or simply email us.
</p>
-
- <h2>Become a Committer and PMC Member</h2>
+
+
+ <h2>Become a Committer and PMC Member</h2>
<p>
We love contributions and gladly promote active contributors to committers and PMC members! If you
are new to Apache Software Foundation then Ignite will be an excellent
@@ -228,9 +227,8 @@ under the License.
This page</a> explains how and when Ignite community members decide to propose contributors to
the roles of committers or PMC members.
</p>
- </section>
-
- <section id="ignite-dev" class="page-section">
+
+
<h2>Start Coding</h2>
<p>
Apache Ignite uses GIT for its VCS system. The "master" branch contains the last released version.
@@ -242,12 +240,12 @@ under the License.
While below you can find quick instructions if you can't wait and want to checkout the Ignite repo,
explore its code and do some changes:
</p>
- <div class="page-heading">GIT checkout</div>
+ <h5>GIT checkout</h5>
<pre class="brush:bash">
# Master branch.
$ git clone https://github.com/apache/ignite.git
</pre>
- <div class="page-heading">Build Project</div>
+ <h5>Build Project</h5>
<pre class="brush:bash">
# Build project.
$ mvn clean install -Pall-java,all-scala,licenses -DskipTests
@@ -256,11 +254,11 @@ under the License.
See more detailed build instructions in the
<a href="https://github.com/apache/ignite/blob/master/DEVNOTES.txt" target="_blank" rel="noopener">DEVNOTES.txt</a> file.
</p>
- </section>
- </main>
- <!--#include virtual="/includes/footer.html" -->
-</main>
+
</div>
+</article>
+<!--#include virtual="/includes/footer.html" -->
+
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/branches/ignite-redisign/community/resources.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/community/resources.html?rev=1875105&r1=1875104&r2=1875105&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/community/resources.html (original)
+++ ignite/site/branches/ignite-redisign/community/resources.html Wed Mar 11 22:11:46 2020
@@ -45,120 +45,102 @@ under the License.
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
- <!--#include virtual="/includes/header.html" -->
-
- <main id="main" role="main" class="container">
- <section id="ask" class="page-section">
- <h1 class="first">Community Resources</h1>
- <p>
- There are many ways you can get help from Apache Ignite community. The <a href="#mail-lists">mailing lists</a>
- are the easiest way to get answers or to get involved with the project. Specifically, if you have any questions
- on how to use Ignite, you should subscribe to the user mailing list:
- <ul class="page-list">
- <li>
- <a href="http://apache-ignite-users.70518.x6.nabble.com/">user@ignite.apache.org</a>
- (<a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
- <a href="http://mail-archives.apache.org/mod_mbox/ignite-user/">archives</a>)
- </li>
- </ul>
- </p>
- </section>
-
- <section id="stackoverflow" class="page-section">
- <h2>Stack Overflow</h2>
- <p>
- Many Ignite community members watch <a href="http://stackoverflow.com/questions/tagged/ignite">Stack Overflow</a>
- for the tag <b>"ignite"</b> or <b>"apacheignite"</b>, so you can post your questions there as well.
- </p>
- </section>
-
- <section id="mail-lists" class="page-section">
- <h2>Mailing Lists</h2>
- <ul class="page-list">
- <li>
- <a href="https://lists.apache.org/list.html?user@ignite.apache.org">user@ignite.apache.org</a> for general questions about Ignite
- (<a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
- <a href="https://lists.apache.org/list.html?user@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">dev@ignite.apache.org</a> for contributor discussions
- (<a href="mailto:dev-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:dev-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-developers.2346864.n4.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">issues@ignite.apache.org</a> for JIRA notifications
- (<a href="mailto:issues-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:issues-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-issues.70530.x6.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?notifications@ignite.apache.org">notifications@ignite.apache.org</a> for GitHub notifications
- (<a href="mailto:notifications-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:notifications-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">commits@ignite.apache.org</a> for GIT commits
- (<a href="mailto:commits-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:commits-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
- </li>
- </ul>
- </section>
-
- <!--<section id="chatroom" class="page-section">-->
- <!--<h2>Chatroom</h2>-->
- <!--<p>-->
- <!--The official chatroom for Apache Ignite is hosted at Gitter: <a href="https://gitter.im/apacheignite/ignite">apacheignite/ignite</a>. Join us there!-->
- <!--<a id="gitter-badge" href="https://gitter.im/apacheignite/ignite">-->
- <!--<img src="https://badges.gitter.im/Join%20Chat.svg" alt="Join the chat at https://gitter.im/apacheignite/ignite" />-->
- <!--</a>-->
- <!--</p>-->
- <!--<p>-->
- <!--You will need a Github account.-->
- <!--</p>-->
- <!--</section>-->
-
- <section id="git" class="page-section">
- <h2>Git Repositories</h2>
- <ul class="page-list">
- <li>Ignite Git: <a href="https://gitbox.apache.org/repos/asf/ignite.git">https://gitbox.apache.org/repos/asf/ignite.git</a></li>
- <li>GitHub Mirror: <a href="https://github.com/apache/ignite">https://github.com/apache/ignite</a></li>
- </ul>
- </section>
-
- <section id="jira" class="page-section">
- <h2>Issue Tracking</h2>
- <p>
- Visit <a href="https://issues.apache.org/jira/browse/IGNITE" target="_blank" rel="noopener">Ignite Jira</a>
- if you would like to file a new issue or view existing issues. If you would like to
- assign an issue to yourself and start contributing, please send an email to the
- <a href="mailto:dev@ignite.apache.org">dev mailing list</a>, so you
- can be granted proper Jira permissions.
- </p>
- </section>
-
- <section id="wiki" class="page-section">
- <h2>Wiki</h2>
- <p>
- Visit <a href="https://cwiki.apache.org/confluence/display/IGNITE/" target="_blank" rel="noopener">Ignite Wiki</a>
- to learn about coding guidelines, release structure, and various design decisions behind Ignite features.
- </p>
- </section>
-
- <section id="people" class="page-section">
- <div class="col-sm-12 col-md-12 col-xs-12" style="padding:0 0 20px 0;">
- <!--<div class="col-sm-6 col-md-8 col-xs-12" style="padding-left:0; padding-right:20px;">-->
+ <!--#include virtual="/includes/header.html" -->
+ <article>
+<div class="container">
+
+ <h1 >Community <strong>Resources</strong></h1>
+ <p>
+ There are many ways you can get help from Apache Ignite community. The <a href="#mail-lists">mailing lists</a> are the easiest way to get answers or to get involved with the project. Specifically, if you have any questions on how to use Ignite, you should subscribe to the user mailing list:
+ </p>
+ <ul class="page-list">
+ <li>
+ <a href="http://apache-ignite-users.70518.x6.nabble.com/">user@ignite.apache.org</a>
+ (<a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
+ <a href="http://mail-archives.apache.org/mod_mbox/ignite-user/">archives</a>)
+ </li>
+ </ul>
+
+
+
+ <section id="stackoverflow" class="page-section">
+ <h2>Stack Overflow</h2>
+ <p>
+ Many Ignite community members watch <a href="http://stackoverflow.com/questions/tagged/ignite">Stack Overflow</a> for the tag <b>"ignite"</b> or <b>"apacheignite"</b>, so you can post your questions there as well.
+ </p>
+ </section>
+
+
+ <section id="mail-lists" class="page-section">
+ <h2>Mailing Lists</h2>
+ <ul class="page-list">
+ <li>
+ <a href="https://lists.apache.org/list.html?user@ignite.apache.org">user@ignite.apache.org</a> for general questions about Ignite
+ <a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
+ <a href="https://lists.apache.org/list.html?user@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">dev@ignite.apache.org</a> for contributor discussions
+ (<a href="mailto:dev-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:dev-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-developers.2346864.n4.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">issues@ignite.apache.org</a> for JIRA notifications
+ (<a href="mailto:issues-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:issues-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-issues.70530.x6.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?notifications@ignite.apache.org">notifications@ignite.apache.org</a> for GitHub notifications
+ (<a href="mailto:notifications-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:notifications-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">commits@ignite.apache.org</a> for GIT commits
+ (<a href="mailto:commits-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:commits-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
+ </li>
+ </ul>
+ </section>
+
+ <section id="git" class="page-section">
+ <h2>Git Repositories</h2>
+ <ul class="page-list">
+ <li>Ignite Git: <a href="https://gitbox.apache.org/repos/asf/ignite.git">https://gitbox.apache.org/repos/asf/ignite.git</a></li>
+ <li>GitHub Mirror: <a href="https://github.com/apache/ignite">https://github.com/apache/ignite</a></li>
+ </ul>
+ </section>
+
+ <section id="jira" class="page-section">
+ <h2>Issue Tracking</h2>
+ <p>
+ Visit <a href="https://issues.apache.org/jira/browse/IGNITE" target="_blank" rel="noopener">Ignite Jira</a>
+ if you would like to file a new issue or view existing issues. If you would like to
+ assign an issue to yourself and start contributing, please send an email to the
+ <a href="mailto:dev@ignite.apache.org">dev mailing list</a>, so you
+ can be granted proper Jira permissions.
+ </p>
+ </section>
+
+
+ <section id="wiki" class="page-section">
+ <h2>Wiki</h2>
+ <p> Visit <a href="https://cwiki.apache.org/confluence/display/IGNITE/" target="_blank" rel="noopener">Ignite Wiki</a> to learn about coding guidelines, release structure, and various design decisions behind Ignite features.</p>
+ </section>
+
+
+ <section id="people" class="page-section">
<h2>Contributers and Committers</h2>
<p>
Visit the <a href="https://github.com/apache/ignite/graphs/contributors">Apache Ignite Contributors page</a>
@@ -228,11 +210,12 @@ under the License.
* - PMC member<br/>
** - PMC chair
</p>
- </div>
- </section>
- </main>
+ </section>
+
+ </div>
+</article>
<!--#include virtual="/includes/footer.html" -->
-</div>
+
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/branches/ignite-redisign/css/ignite-redesign.css
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/css/ignite-redesign.css?rev=1875105&r1=1875104&r2=1875105&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/css/ignite-redesign.css (original)
+++ ignite/site/branches/ignite-redisign/css/ignite-redesign.css Wed Mar 11 22:11:46 2020
@@ -7504,16 +7504,9 @@ strong {
#main-banner h1 {
font-weight: 300;
font-size: 30px;
- line-height: 1.4em;
- text-align: center;
- }
+ line-height: 1.4em; }
#main-banner h1 strong {
display: block; }
-
- #main-banner .buttons {
- text-align: center;
- align-items: center;}
-
#main-banner p {
font-size: 24px;
font-weight: 300;
@@ -7551,6 +7544,22 @@ strong {
padding: 4rem 0;
background-color: #ffffff;
box-shadow: inset 0px 15px 8px -10px #e5e5e5; }
+ #home-use-cases #intro-text {
+ margin-bottom: 50px; }
+ #home-use-cases #intro-text p {
+ background-color: #f2f2f2;
+ border-radius: 5px;
+ padding: 40px 90px;
+ font-size: 18px;
+ line-height: 2em; }
+ #home-use-cases #intro-text:after {
+ content: "";
+ width: 25vw;
+ height: 6px;
+ background-color: #f2f2f2;
+ display: block;
+ margin: 40px auto 50px;
+ border-radius: 5px; }
#home-use-cases .container .row {
margin-bottom: 25px; }
#home-use-cases .container h2 {
@@ -7589,7 +7598,7 @@ section.section-block h2 {
text-align: center;
font-size: 32px;
text-transform: uppercase;
- margin-bottom: 5px; }
+ margin-bottom: 1em; }
section.section-block h2 strong {
color: #055799;
font-weight: 900; }
@@ -7638,63 +7647,6 @@ section.section-block h2 {
background-color: #b02032;
fill: #ffffff; }
-#home-deployment-options {
- box-shadow: inset 0px 15px 8px -10px #e5e5e5, inset 0px -15px 8px -10px #e5e5e5; }
-
- #home-deployment-options #intro-text {
- margin-bottom: 50px; }
-
- #home-deployment-options #intro-text p {
- border-radius: 5px;
- padding: 45px 90px;
- font-size: 18px;
- text-align: center;
- line-height: 2em; }
-
- #home-deployment-options #intro-text:after {
- content: "";
- width: 25vw;
- height: 6px;
- background-color: #f2f2f2;
- display: block;
- margin: 10px auto 10px;
- border-radius: 5px; }
-
- #home-deployment-options .row {
- padding: 0 3rem; }
- #home-deployment-options .option {
- padding: 0 40px; }
- #home-deployment-options .option a {
- display: block;
- text-align: center;
- color: #000;
- margin-bottom: 3em; }
- #home-deployment-options .option a h3 {
- font-size: 20px;
- line-height: 1.5em;
- font-weight: 600; }
- #home-deployment-options .option a h3 span {
- display: block; }
- #home-deployment-options .option a p {
- font-size: 16px;
- font-weight: 400;
- line-height: 1.6em; }
- #home-deployment-options .option a svg {
- width: 100px;
- height: 100px;
- fill: #b02032;
- transition: all 0.5s ease-in-out;
- background-color: #ffffff;
- border-radius: 0px;
- padding: 1.5em;
- margin-top: 2em;
- margin-bottom: 1em; }
- #home-deployment-options .option a:hover {
- text-decoration: none; }
- #home-deployment-options .option a:hover svg {
- background-color: #b02032;
- fill: #ffffff; }
-
#home-extras {
padding: 4rem 0; }
#home-extras #home-links ul {
@@ -7735,16 +7687,16 @@ section.section-block h2 {
text-align: right;
margin-top: 10px; }
-section.internal-page {
+.documentation {
padding-top: 0; }
- section.internal-page h2 {
+ .documentation h2 {
text-align: center;
text-transform: uppercase;
font-weight: 400;
font-size: 24px;
margin-top: 4em;
margin-bottom: 1em; }
- section.internal-page h2:after {
+ .documentation h2:after {
content: " ";
display: block;
width: 200px;
@@ -7752,16 +7704,16 @@ section.internal-page {
border-top: 1px solid #dddddd;
margin: 1.5em auto 0;
height: 7px; }
- section.internal-page p.intro {
+ .documentation p.intro {
text-align: center;
padding: 0 3em;
font-size: 16px;
margin-bottom: 2em; }
- section.internal-page .icons-list {
+ .documentation .icons-list {
padding-left: 0; }
- section.internal-page .icons-list li {
+ .documentation .icons-list li {
list-style: none; }
- section.internal-page .icons-list li a {
+ .documentation .icons-list li a {
color: #000;
text-align: center;
display: block;
@@ -7771,14 +7723,14 @@ section.internal-page {
line-height: 1.6em;
margin-bottom: 4em;
transition: all 0.25s ease-in-out; }
- section.internal-page .icons-list li a svg {
+ .documentation .icons-list li a svg {
margin: 0 auto;
display: block;
width: 3.5em;
min-height: 5em;
fill: #c8c8c8;
transition: all 0.25s ease-in-out; }
- section.internal-page .icons-list li a:after {
+ .documentation .icons-list li a:after {
content: "";
border-right: 1px solid #cccccc;
height: 6em;
@@ -7788,13 +7740,125 @@ section.internal-page {
position: absolute;
right: 0;
top: calc(50% - 4em); }
- section.internal-page .icons-list li a:hover {
+ .documentation .icons-list li a:hover {
color: #ed1c24; }
- section.internal-page .icons-list li a:hover svg {
+ .documentation .icons-list li a:hover svg {
fill: #ed1c24; }
- section.internal-page .icons-list li:last-child a:after, section.internal-page .icons-list li:nth-child(4n) a:after {
+ .documentation .icons-list li:last-child a:after, .documentation .icons-list li:nth-child(4n) a:after {
display: none; }
+/***
+* Styles for internal pages
+*/
+article {
+ padding: 80px 0;
+ font-size: 16px;
+ line-height: 2em; }
+ article h1, article h2 {
+ font-size: 36px;
+ font-weight: 300;
+ text-transform: uppercase;
+ margin-bottom: 60px; }
+ article h1 strong, article h2 strong {
+ font-weight: bold;
+ color: #055799; }
+ article h2 {
+ font-size: 26px;
+ margin-top: 50px;
+ margin-bottom: 30px; }
+ article h3 {
+ font-size: 26px;
+ font-weight: 500;
+ margin-top: 40px;
+ margin-bottom: 20px; }
+ article .fa-anchor {
+ font-size: 14px; }
+ article ul li {
+ margin-bottom: 1em; }
+ article .tab-content {
+ margin-top: 30px;
+ margin-bottom: 40px; }
+ article .jumbotron {
+ margin-top: 80px;
+ padding: 2rem;
+ clear: both; }
+ article .jumbotron .title {
+ font-size: 26px;
+ font-weight: 500; }
+ article img.diagram-right {
+ max-width: 50%;
+ float: right;
+ margin: 0 0 2rem 2rem; }
+ article .fact-question {
+ padding-bottom: 35px; }
+ article .nav-tabs > li > a {
+ margin-right: 2px;
+ line-height: 1.42857;
+ border: 1px solid transparent;
+ border-radius: 4px 4px 0 0; }
+ article .nav > li > a {
+ position: relative;
+ display: block;
+ padding: 10px 15px;
+ overflow: hidden; }
+ article .nav-tabs > li {
+ float: left;
+ margin-bottom: -1px; }
+ article .nav-tabs > li > a.active, article .nav-tabs > li.active > a, article .nav-tabs > li.active > a:hover, article .nav-tabs > li.active > a:focus {
+ color: #555555;
+ background-color: #fff;
+ border: 1px solid #ddd;
+ border-bottom-color: transparent;
+ cursor: default; }
+ article .nav-tabs {
+ border-bottom: 1px solid #ddd; }
+ article #events .row-event {
+ margin-bottom: 4rem;
+ border-bottom: 2px #e1e1e1 dotted;
+ padding-bottom: 2rem; }
+ article #events .row-event .round-icon-block {
+ background-color: #f2f2f2;
+ border-radius: 10px;
+ padding: 1rem; }
+ article #events .row-event .round-icon-block img {
+ margin: 0 auto;
+ max-width: 75%;
+ display: block; }
+ article #events .row-event .round-icon-block p {
+ text-align: center;
+ margin-top: 10px;
+ font-weight: 300; }
+ article #events .row-event h3 {
+ margin-top: 0;
+ margin-bottom: 10px; }
+ article #events .row-event .event-date {
+ font-size: 15px;
+ color: #666;
+ margin-bottom: 10px; }
+ article #meetups-groups #meetups-tabs .round-icon-block-tab {
+ background-color: #f2f2f2;
+ border-radius: 10px;
+ padding: 5px;
+ display: block;
+ float: left;
+ margin-right: 8px; }
+ article #meetups-groups #meetups-tabs .round-icon-block-tab img {
+ margin: 0px auto;
+ max-width: 20px;
+ width: 20px;
+ display: block; }
+ article #meetups-groups #meetups-tabs .continent {
+ display: block;
+ float: left; }
+ article #meetups-groups #meetups-tabs .active .continent {
+ font-weight: bold;
+ padding-top: 1px; }
+ article #meetups-groups .meet-groups h4 {
+ font-size: 1.2rem;
+ font-weight: 600; }
+ article #meetups-groups .meet-groups ul {
+ padding-bottom: 25px; }
+
@media (max-width: 1400px) {
#main-banner .wrapper {
background: -moz-linear-gradient(45deg, #187ccc 0%, #0a5a9a 9%, rgba(242, 242, 242, 0) 9%, rgba(242, 242, 242, 0) 90%, #0a5a9a 90%, #187ccc 100%);
@@ -7901,8 +7965,7 @@ section.internal-page {
font-size: 26px;
text-align: center; }
#main-banner .buttons {
- text-align: center;
- align-items: center;}
+ text-align: center; }
#main-banner .btn {
margin-bottom: 10px; }
#home-use-cases #tabsContent .txt-wrapper {
Modified: ignite/site/branches/ignite-redisign/docs-and-apis.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/docs-and-apis.html?rev=1875105&r1=1875104&r2=1875105&view=diff
==============================================================================
Binary files - no diff available.