Author: dmagda
Date: Thu Aug 24 01:18:55 2017
New Revision: 1805985
URL: http://svn.apache.org/viewvc?rev=1805985&view=rev
Log:
added distributed database use case
Added:
ignite/site/trunk/use-cases/database/distributed-database.html (with
props)
Added: ignite/site/trunk/use-cases/database/distributed-database.html
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/distributed-database.html?rev=1805985&view=auto
==============================================================================
--- ignite/site/trunk/use-cases/database/distributed-database.html (added)
+++ ignite/site/trunk/use-cases/database/distributed-database.html Thu Aug 24
01:18:55 2017
@@ -0,0 +1,140 @@
+<!--
+ âââ ââââââ âââ ââââââ
âââ ââ ââââââ âââ âââââ
ââââ â ââââââââââââââââââ
+ââââââ ââââ âââââââââ
ââââ ââ ââââ âââââ â ââââ
âââ âââ ââ ââ â âââââ âââ ââââ
â
+âââ âââ ââââ âââââââ âââ âââ
â ââââââââââââ
âââââââââââââââ ââ ââââââââ
ââââ ââââââ
+âââââââââ âââââââ
ââââââââââ ââââ âââââââ âââ
âââ â âââââââ âââââââ
ââââââââââ ââââ â âââ â
+ ââ ââââââââ â â ââ âââââ
âââââ ââââââââââââââââ
ââââââââââââââââ ââââââââ
ââââ â âââââââ
+ ââ ââââââââ â â ââ âââââ ââ
â â â âââââââ ââ â ââ ââ â â
ââ â â ââ â ââ ââ ââ â
+ â ââ âââ â â ââ â â â â âââ
â â â â â â â â â ââ â ââ â â â
â â â
+ â â ââ â â â â ââ â â
â ââ â â â â â â â â â
+ â â â ââ â â â â â â
â â â â â â
+-->
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<!DOCTYPE html>
+<html>
+<head>
+ <link rel="canonical"
href="https://ignite.apache.org/use-cases/database/distributed-database.html"/>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+ <title>Distributed Database - Apache Ignite</title>
+ <link media="all" rel="stylesheet" href="/css/all.css?v=1.8">
+ <link
href="https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css";
rel="stylesheet">
+ <link media="all" rel="stylesheet" href="/css/syntaxhighlighter.css">
+ <link
href='https://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,600italic,700,700italic,800,800italic'
rel='stylesheet' type='text/css'>
+
+ <!--#include virtual="/includes/sh.html" -->
+</head>
+<body>
+<div id="wrapper">
+ <!--#include virtual="/includes/header.html" -->
+
+ <main id="main" role="main" class="container">
+ <section id="key-value-store" class="page-section">
+ <h1 class="first">Distributed Database</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>
+ Apache Ignite can be used as all-in-one distributed
database that supports SQL, key-value,
+ compute, machine learning and other data processing
APIs.
+ </p>
+ <p>
+ Regardless of the API you decide to use, the data is
always stored in a form of key-value pairs
+ across the cluster. The underlying key-value store
distributes the data evenly guaranteeing that
+ every cluster node will own a portion of the overall
data set.
+ </p>
+ <p>
+ When a piece of data is received by a cluster node,
the node can put it both in RAM and on disk
+ and process from two memory tiers equally well thanks
to the
+ <a href="/features/durablememory.html"
target="_blank">Durable Memory</a> architecture.
+ The data can be persisted in <a
href="/features/persistence.html" target="_blank">
+ Ignite Native Persistence</a> or in a 3rd party
database such as RDBMS, NoSQL or Hadoop.
+ <a
href="https://apacheignite.readme.io/docs/distributed-persistent-store";
target="_blank">Learn</a>
+ when to use one type of persistence over another.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-5 col-xs-12"
style="padding-right:0">
+ <img class="img-responsive"
src="/images/ignite-distributed-database.png" width="400px"
style="float:right;"/>
+ </div>
+ </div>
+
+ <div class="page-heading">SQL</div>
+ <p>
+ Ignite complies with SQL ANSI-99 standard supporting all
<b>SQL</b> and <b>DML</b> commands,
+ including SELECT, UPDATE, INSERT, MERGE, DELETE statements and
distributed joins. It also provides
+ support for a subset of <b>DDL</b> commands relevant for
distributed SQL databases. Read more about
+ Ignite's <a href="/use-cases/database/sql-database.html"
target="_blank">SQL capabilities</a>.
+ </p>
+
+ <div class="page-heading">Key-value</div>
+ <p>
+ Apache Ignite key-value APIs are compliant with <a
href="/use-cases/caching/jcache-provider.html" target="_blank">
+ JCache (JSR 107)</a> specification and provide extended
features built on top such as
+ distributed ACID transactions, scan and continuous queries,
collocated processing. Read more about
+ Ignite's <a href="/use-cases/database/key-value-database.html"
class="text-nowrap" target="_blank">
+ key-value database (Data Grid) capabilities</a>.
+ </p>
+ <div class="page-heading">Collocated Processing</div>
+ <p>
+ The disk-centric systems, like RDBMS or NoSQL, generally
utilize the classic client-server
+ approach, where the data is brought from the server to the
client side where it gets processed
+ and then is 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>
+ A much more scalable approach is <a
href="/collocatedprocessing.html" target="_blank">
+ collocated processing</a> that reverses the flow by bringing
the computations to the servers where
+ the data actually resides. This approach allows you to execute
advanced logic or distributed SQL
+ with JOINs exactly where the data is stored avoiding expensive
serialization and network trips.
+ </p>
+ <div class="page-heading">Partitioning & Replication</div>
+ <p>
+ Depending on configuration, Ignite can either partition or
replicate data.
+ Unlike <code>REPLICATED</code> mode, where data is fully
replicated across all nodes
+ in the cluster, in <code>PARTITIONED</code> mode Ignite will
equally split the data across
+ multiple cluster nodes, allowing for staring TBs of data both
in memory and on disk.
+ </p>
+ <div class="page-heading">Redundancy</div>
+ <p>
+ Ignite also allows to configure multiple <b>backup copies</b>
to guarantee data resiliency
+ in case of failures.
+ </p>
+ <div class="page-heading">Consistency</div>
+ <p>
+ Regardless of which replication scheme is used, Ignite
guarantees data consistency across
+ all cluster members.
+ </p>
+ <p>
+ Check <a href="/features/sql.html" target="_blank">SQL</a>,
+ <a href="/features/datagrid.html" class="text-nowrap"
target="_blank">Data Grid</a>, and
+ <a href="/features/computegrid.html" class="text-nowrap"
target="_blank">Compute Grid</a>
+ features sections for more technical details.
+ </p>
+ </section>
+ </main>
+
+ <!--#include virtual="/includes/footer.html" -->
+</div>
+<!--#include virtual="/includes/scripts.html" -->
+</body>
+</html>
Propchange: ignite/site/trunk/use-cases/database/distributed-database.html
------------------------------------------------------------------------------
svn:mime-type = text/plain
