Author: dmagda
Date: Thu Feb 13 18:49:24 2020
New Revision: 1873986
URL: http://svn.apache.org/viewvc?rev=1873986&view=rev
Log:
Updated clustering and multi-language support pages.
Removed:
ignite/site/branches/ignite-redisign/features/igniterdd.html
ignite/site/branches/ignite-redisign/features/runseverywhere.html
Modified:
ignite/site/branches/ignite-redisign/.htaccess
ignite/site/branches/ignite-redisign/arch/clustering.html
ignite/site/branches/ignite-redisign/features/multilanguage.html
ignite/site/branches/ignite-redisign/includes/header.html
Modified: ignite/site/branches/ignite-redisign/.htaccess
URL:
http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/.htaccess?rev=1873986&r1=1873985&r2=1873986&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/.htaccess (original)
+++ ignite/site/branches/ignite-redisign/.htaccess Thu Feb 13 18:49:24 2020
@@ -33,6 +33,8 @@ Redirect 301 /provenusecases.html /use-c
Redirect 301 /features/datavisualization.html /features/manageandmonitor.html
Redirect 301 /addons.html /features.html
Redirect 301 /arch/durablememory.html /arch/memorycentric.html
+Redirect 301 /features/runseverywhere.html /features/multilanguage.html
+Redirect 301 /features/igniterdd.html /use-cases/spark-acceleration.html
RewriteEngine On
Modified: ignite/site/branches/ignite-redisign/arch/clustering.html
URL:
http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/arch/clustering.html?rev=1873986&r1=1873985&r2=1873986&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/arch/clustering.html (original)
+++ ignite/site/branches/ignite-redisign/arch/clustering.html Thu Feb 13
18:49:24 2020
@@ -39,6 +39,7 @@ under the License.
<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>Deploy Anywhere - Apache Ignite</title>
<!--#include virtual="/includes/styles.html" -->
@@ -54,19 +55,19 @@ under the License.
<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 cluster is based on the shared-nothing
architecture which implies that all the
- cluster nodes are equal, independent and
self-sufficient, and there is no single point of failure
- across the cluster.
+ Apache Ignite implements the shared-nothing
architecture when all the cluster nodes are equal
+ and self-sufficient, and there is no single point of
failure or bottleneck across the cluster.
+ Ignite does NOT have a component such as a master node
or name node that presents in many
+ distributed systems.
</p>
<p>
- Ignite nodes can automatically discover each other
relying on flexible Discovery SPI component.
- This helps to scale the cluster out or down when
needed and easily.
+ Ignite nodes discover each automatically in your
environment, and the cluster can be scaled out or in easily.
</p>
<p>
- Apache Ignite can run stand-alone, in a cluster,
within Kubernetes and Docker containers, as well
- as on Apache Mesos and Hadoop Yarn. It can also run on
physical servers as well as within
- virtual environments or clouds. Technically there are
no limitations on where the cluster
- can be deployed.
+ Apache Ignite can run on bare metal, virtual machines,
Docker, Kubernetes, and cloud
+ environments. Technically there are no limitations in
regards to deployment environments --
+ as long as the nodes can auto-discover each other via
the TCP/IP interface, the cluster can be
+ launched anywhere.
</p>
</div>
<div class="col-sm-6 col-md-6 col-xs-12"
style="padding-right:0;">
@@ -76,204 +77,50 @@ under the License.
<div class="page-heading">Servers, Clients and Protocols</div>
<p>
- There are two types of nodes defined in Ignite - client and
server nodes. The nodes server a
- different purpose.
+ Ignite defines two types of nodes â servers and clients.
+
+ 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. Those
resources are pooled and become available to
+ Ignite applications once the server node joins a cluster of
other server nodes.
</p>
<p>
- The server nodes act as containers for data and computations.
Once interconnected, the server nodes will
- represent a distributed database (or data grid) that stores
the data, participates in queries processing,
- compute execution, stream processing, etc.
+ 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>
- The client nodes, on their turn, provide an ability to connect
to the distributed database (a group of server nodes)
- remotely. Ignite native clients allow using the whole set of
Ignite APIs, including SQL, transactions,
- compute, streaming, services, etc. from the client side.
+ 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
+ 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 client nodes, you can access the cluster by
means of Ignite binary client protocol,
+ In addition to the thick clients nodes, you can access the
cluster with Ignite thin clients,
JDBC and ODBC drivers, or REST API.
</p>
- <div class="page-heading">Cloud Native Database</div>
+ <div class="page-heading">Learn More</div>
<p>
- Cloud native technologies allow us to build and run scalable
applications in public, private and
- hybrid environments. Ignite is a <a
href="https://landscape.cncf.io/landscape=database-and-data-warehouse";
target="_blank" rel="noopener">
- cloud native database</a> designed specifically for a cloud
- computing architecture.
- </p>
- <p>
- Ignite has native integration with <code
class="text-nowrap">Amazon AWS</code>
- and <code class="text-nowrap">Google Compute Engine</code>.
For all other cloud environments, Ignite
- integrates with <code class="text-nowrap">Apache
JClouds</code> that has support for most of the
- <a href="https://jclouds.apache.org/reference/providers/";
target="_blank" rel="noopener" class="text-nowrap">existing
- cloud providers</a>.
- </p>
- <div class="page-heading">Containers</div>
- <p>
- Ignite can freely run within container environments. Ignite's
integration with <code>Docker</code>
- allows to automatically build and deploy user code into Ignite
prior to server startup.
- </p>
- <p>
- Apache Ignite cluster can also be deployed in
<code>Kubernetes</code> that allows automatic deployment and management of
- containerized applications.
- </p>
-
- <div class="page-heading">Resource Managers</div>
- <p>
- Ignite provides native integration for <code
class="text-nowrap">Hadoop Yarn</code>,<code>Kubernetes</code>,
- and <code class="text-nowrap">Apache Mesos</code> making it
very easy to seamlessly deploy Ignite
- into specific environments and manage it there.
- </p>
-
- <div class="page-heading">More on Clustering and Deployment</div>
- <table class="formatted" name="Deployment Options Features">
- <thead>
- <tr>
- <th width="35%" class="left">Feature</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="left">Clients and Servers</td>
- <td>
- <p>
- There are two types of nodes defined in Ignite -
client and server nodes. The nodes server a
- different purpose:
- </p>
- <div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/clients-vs-servers";
target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Self-Healing Cluster</td>
- <td>
- <p>
- Ignite cluster can self-heal, where clients
automatically reconnect in case of failures,
- slow clients are automatically kicked out, and
data from failed nodes
- is automatically propagated to other nodes in the
grid:
- </p>
- <div class="page-links">
- <a
href="http://apacheignite.readme.io/docs/clients-vs-servers"; target="docs">Docs
for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Cross-platform Support</td>
- <td>
- <p>
- Applications can access the cluster from numerous
programming languages as well as JDBC/ODBC
- drivers, and additional protocols:
- </p>
- <div class="page-links">
- <a href="/features/multilanguage.html"
target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Zero Deployment</td>
- <td>
- <p>
- Ignite nodes automatically become aware of custom
classes, eliminating the need to explicitly deploy them:
- </p>
- <div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/zero-deployment"; target="docs">Docs
for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Dynamic Schema Changes</td>
- <td>
- <p>
- Ignite stores objects in binary format eliminating
the need to deploy classes on server nodes:
- </p>
- <div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/binary-marshaller"; target="docs">Docs
for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Stand-Alone Clusters</td>
- <td>
- <p>
- Ignite nodes can automatically discover each
other. This helps to scale the cluster
- when needed, without having to restart the whole
cluster - simply start up new additional
- nodes and they will automatically join the
existing work loads:
- </p>
- <div class="page-links">
- <a
href="http://apacheignite.readme.io/docs/cluster"; target="docs">Docs for this
Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Docker Container</td>
- <td>
- <p>
- <code>Docker</code> allows to package Ignite
deployment with all the dependencies into a
- standard container. Docker automates downloading
the Ignite release, deploying users'
- code into Ignite, and configuring nodes. It also
automatically starts up the fully
- configured Ignite node:
- </p>
- <div class="page-links">
- <a
href="http://apacheignite.readme.io/docs/docker-deployment"; target="docs">Docs
for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Kubernetes</td>
- <td>
- <p>
- Apache Ignite cluster can be easily deployed in
and maintained by <code>Kubernetes</code> which is an
- open-source system for automating deployment,
scaling, and management of containerized applications:
- </p>
- <div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/kubernetes-deployment";
target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Public Clouds</td>
- <td>
- <p>
- For public cloud environments, Ignite has native
integration with <code class="text-nowrap">Amazon AWS</code>
- and <code class="text-nowrap">Google Compute
Engine</code>. For all other cloud environments, Ignite
- integrates with <code class="text-nowrap">Apache
JClouds</code> which has support for most of the
- <a
href="https://jclouds.apache.org/reference/providers/"; target="_blank"
rel="noopener" class="text-nowrap">existing cloud providers</a>.
- </p>
- <div class="page-links" style="line-height: 1.3;">
- <a
href="https://apacheignite-mix.readme.io/docs/amazon-aws"; target="docs">Amazon
AWS Integration <i class="fa fa-angle-double-right"></i></a><br/>
- <a
href="https://apacheignite-mix.readme.io/docs/google-compute-engine";
target="docs">Google Cloud Integration <i class="fa
fa-angle-double-right"></i></a><br/>
- <a
href="https://apacheignite-mix.readme.io/docs/jclouds"; target="docs">Apache
JClouds Integration <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Apache Mesos</td>
- <td>
- <p>
- Ignite provides native integration for
<code>Apache Mesos</code> making it very easy
- to deploy into Mesos data centers, such as, for
example, Hadoop and Spark environments:
- </p>
- <div class="page-links">
- <a
href="http://apacheignite.readme.io/docs/mesos-deployment"; target="docs">Docs
for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Hadoop Yarn</td>
- <td>
- <p>
- Ignite provides native integration for
<code>Hadoop Yarn</code> making it very easy
- to deploy into Hadoop and Spark environments:
- </p>
- <div class="page-links">
- <a
href="http://apacheignite.readme.io/docs/yarn-deployment"; target="docs">Docs
for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- </tbody>
- </table>
+ <a href="https://apacheignite.readme.io/docs/clustering";
target="docs">
+ <b>Ignite Clustering Documentation <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>
Modified: ignite/site/branches/ignite-redisign/features/multilanguage.html
URL:
http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/features/multilanguage.html?rev=1873986&r1=1873985&r2=1873986&view=diff
==============================================================================
Binary files - no diff available.
Modified: ignite/site/branches/ignite-redisign/includes/header.html
URL:
http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/includes/header.html?rev=1873986&r1=1873985&r2=1873986&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/includes/header.html (original)
+++ ignite/site/branches/ignite-redisign/includes/header.html Thu Feb 13
18:49:24 2020
@@ -66,14 +66,6 @@
onclick="ga('send', 'event',
'apache_ignite_features', 'menu_click', 'machine_learning');">
Machine Learning</a>
</li>
- <li><a
href="/features/multilanguage.html" aria-label="Multilanguage"
- onclick="ga('send', 'event',
'apache_ignite_features', 'menu_click', 'multi_language');">
- Multi-Language</a>
- </li>
- <li><a href="/arch/clustering.html"
aria-label="Clustering"
- onclick="ga('send', 'event',
'apache_ignite_features', 'menu_click', 'clustering');">
- Deploy Anywhere</a>
- </li>
<li><a href="/features.html"><i>More
Features</i></a></li>
<li class="divider">
