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 2018/01/11 01:11:57 UTC
svn commit: r1820814 - /ignite/site/trunk/whatisignite-2.html
Author: dmagda
Date: Thu Jan 11 01:11:57 2018
New Revision: 1820814
URL: http://svn.apache.org/viewvc?rev=1820814&view=rev
Log:
reworking what's ignite page
Added:
ignite/site/trunk/whatisignite-2.html
- copied, changed from r1820811, ignite/site/trunk/whatisignite.html
Copied: ignite/site/trunk/whatisignite-2.html (from r1820811, ignite/site/trunk/whatisignite.html)
URL: http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?p2=ignite/site/trunk/whatisignite-2.html&p1=ignite/site/trunk/whatisignite.html&r1=1820811&r2=1820814&rev=1820814&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite-2.html Thu Jan 11 01:11:57 2018
@@ -66,55 +66,28 @@ under the License.
</div>
</section>
- <section id="whatisignite-feature-desc" class="page-section" style="border: none;">
- <div class="col-sm-12 col-md-12 col-xs-12">
- <h3>Durable Memory</h3>
- <p>
- Ignite's durable memory component treats RAM not just as a caching layer but as a complete fully functional storage layer.
- This means that users can turn the persistence on and off as needed. If the persistence is off, then Ignite
- can act as a distributed <nobr><i><a href="/use-cases/database/in-memory-database.html">in-memory database</a></i></nobr> or <nobr><i><a href="/features/datagrid.html">in-memory data grid</a></i></nobr>,
- depending on whether you prefer to use SQL or key-value APIs. If the persistence is turned on, then Ignite becomes a distributed,
- <nobr><i><a href="/features/sql.html">horizontally scalable database</a></i></nobr> that guarantees full data consistency and is
- resilient to full cluster failures.
- </p>
- <h3>Ignite Persistence</h3>
- <p>
- Ignite <a href="/features/persistence.html">native persistence</a> is a distributed,
- strongly consistent disk store that transparently integrates with Ignite's <i>durable memory</i>.
- </p>
- <h3>ACID Compliance</h3>
- <p>
- Data stored in Ignite is ACID-compliant both in memory and on disk, making Ignite a <i><strong>strongly consistent</strong></i> system.
- Ignite transactions work across the network and can span multiple servers.
- </p>
-
- <h3>Complete SQL Support</h3>
- <p>
- Ignite provides full support for SQL, DDL and DML, allowing users to interact with Ignite using pure SQL without writing any code.
- This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes Ignite a one-of-a-kind
- <i><a href="/features/sql.html">distributed SQL database</a></i>.
- </p>
-
- <h3>Key-Value</h3>
- <p>
- The in-memory data grid component in Ignite is a fully transactional <i><a href="/use-cases/database/key-value-store.html">distributed key-value store</a></i> that can scale horizontally
- across 100s of servers in the cluster. When persistence is enabled, Ignite can also store more data than fits in memory and survive full cluster restarts.
- </p>
-
- <h3>Collocated Processing</h3>
- <p>
- Most traditional databases work in a client-server fashion, meaning that data must be brought to the client side for processing. This approach requires
- lots of data movement from servers to clients and generally does not scale. Ignite, on the other hand, allows for sending light-weight computations to the data,
- i.e. <nobr><i><a href="/collocatedprocessing.html">collocating computations with data</a></i></nobr>. As a result, Ignite scales better and minimizes data movement.
- </p>
-
- <h3>Scalability and Durability</h3>
- <p>
- Ignite is an elastic, horizontally scalable distributed system that supports adding and removing cluster nodes on demand. Ignite also allows for
- storing multiple copies of the data, making it resilient to partial cluster failures. If the persistence is enabled, then data stored in Ignite
- will also survive full cluster failures. Cluster restarts in Ignite can be very fast, as the data becomes operational instantaneously directly from disk.
- As a result, the data does not need to be preloaded in-memory to begin processing, and Ignite caches will lazily warm up resuming the in memory performance.
- </p>
+ <section id="features-and-use-cases" class="page-section">
+ <div class="col-sm-12 col-md-12 col-xs-12 page-menu">
+ <div class="col-sm-6 col-md-6 col-xs-12">
+ <h3>Main Features</h3>
+ <ul>
+ <li><a href="/features/durablememory.html">Durable Memory</a></li>
+ <li><a href="/features/persistence.html">Persistence</a></li>
+ <li><a href="/features/sql.html">Distributed SQL</a></li>
+ <li><a href="/features/computegrid.html">Compute Grid</a></li>
+ <li><a href="/features/machinelearning.html">Machine Learning<sup>βeta</sup></a></li>
+ </ul>
+ </div>
+ <div class="col-sm-6 col-md-6 col-xs-12">
+ <h3>Use Cases</h3>
+ <ul>
+ <li><a href="/features/datagrid.html">Data Grid</a></li>
+ <li><a href="/use-cases/caching/database-caching.html">Database Caching</a></li>
+ <li><a href="/use-cases/database/distributed-database.html">Distributed Database</a></li>
+ <li><a href="/use-cases/database/in-memory-database.html">In-Memory Database</a></li>
+ <li><a href="/use-cases/database/sql-database.html">SQL Database</a></li>
+ </ul>
+ </div>
</div>
</section>