use-cases/compare/coherence.html - ignite-website

<!--

▄▄▄ ██▓███ ▄▄▄ ▄████▄ ██░ ██ ▓█████ ██▓ ▄████ ███▄ █ ██▓▄▄▄█████▓▓█████

▒████▄ ▓██░ ██▒▒████▄ ▒██▀ ▀█ ▓██░ ██▒▓█ ▀ ▓██▒ ██▒ ▀█▒ ██ ▀█ █ ▓██▒▓ ██▒ ▓▒▓█ ▀

▒██ ▀█▄ ▓██░ ██▓▒▒██ ▀█▄ ▒▓█ ▄ ▒██▀▀██░▒███ ▒██▒▒██░▄▄▄░▓██ ▀█ ██▒▒██▒▒ ▓██░ ▒░▒███

░██▄▄▄▄██ ▒██▄█▓▒ ▒░██▄▄▄▄██ ▒▓▓▄ ▄██▒░▓█ ░██ ▒▓█ ▄ ░██░░▓█ ██▓▓██▒ ▐▌██▒░██░░ ▓██▓ ░ ▒▓█ ▄

▓█ ▓██▒▒██▒ ░ ░ ▓█ ▓██▒▒ ▓███▀ ░░▓█▒░██▓░▒████▒ ░██░░▒▓███▀▒▒██░ ▓██░░██░ ▒██▒ ░ ░▒████▒

▒▒ ▓▒█░▒▓▒░ ░ ░ ▒▒ ▓▒█░░ ░▒ ▒ ░ ▒ ░░▒░▒░░ ▒░ ░ ░▓ ░▒ ▒ ░ ▒░ ▒ ▒ ░▓ ▒ ░░ ░░ ▒░ ░

▒ ▒▒ ░░▒ ░ ▒ ▒▒ ░ ░ ▒ ▒ ░▒░ ░ ░ ░ ░ ▒ ░ ░ ░ ░ ░░ ░ ▒░ ▒ ░ ░ ░ ░ ░

░ ▒ ░░ ░ ▒ ░ ░ ░░ ░ ░ ▒ ░░ ░ ░ ░ ░ ░ ▒ ░ ░ ░

░ ░ ░ ░░ ░ ░ ░ ░ ░ ░ ░ ░ ░ ░ ░ ░

-->

<!--

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

KIND, either express or implied. See the License for the

specific language governing permissions and limitations

under the License.

-->

<!DOCTYPE html>

<html>

<head>

<title>Apache Ignite vs Coherence</title>

</head>

<body>

<h2 class="first">Ignite vs Coherence</h2>

Both, Apache Ignite and Oracle Coherence provide a feature rich data grid functionality responsible for

partitioning and caching data in memory with the capability to scale out across distributed clusters.

Ignite and Coherence have many differences in the way caching, transactions, and data querying

are supported. Below we outline only major differences, which in our opinion are most important whenever

choosing an in-memory data grid product.

</section>

<thead>

<tr>

<th style="text-align: center;font-size: larger">Apache Ignite</th>

<th style="text-align: center;font-size: larger">Coherence</th>

</tr>

</thead>

<tbody>

<tr><td colspan="2" style="text-align: center">Open Source vs. Closed Source</td></tr>

<tr>

Ignite is an Apache project and has been growing and enhancing its open source feature set. The latest

major additions include Ignite Fabric for C++ and .NET/C#, with

Node.JS integration coming soon as well.

</td>

Coherence is a proprietary Oracle software and does not have a free open source offering.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">JCache (JSR 107)</td></tr>

<tr>

Ignite is fully compliant with JCache (JSR 107) specification for caching.

</td>

Coherence is fully compliant with JCache (JSR 107) specification for caching.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">Off-Heap Memory</td></tr>

<tr>

Ignite supports storing data in on-heap or off-heap memory,

depending on user configuration.

</td>

Oracle Coherence does provide developers with a limited option to store the data in off-heap memory.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">Off-Heap Indexes</td></tr>

<tr>

Whenever configured with off-heap memory, Ignite will store query indexes

off-heap as well (in order not to affect on-heap memory used by user applications).

</td>

Coherence does not have support for off-heap indexes.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">SQL Queries</td></tr>

<tr>

Ignite supports complete SQL (ANSI-99) syntax for querying in-memory data.

</td>

Coherence does not support SQL.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">Queries with JOINs</td></tr>

<tr>

Ignite SQL includes full support for SQL JOINs, including

JOINs across multiple caches, for example:

select * from A a, B b where a.b_id = b.id

</td>

Coherence does not have any support for JOIN queries (with or without SQL).

Whenever needed, users perform JOINs by manually combining multiple query results.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">ACID Transactions</td></tr>

<tr>

Ignite transactions provide excellent performance with 100s of thousands transactions/sec per server.

</td>

Coherence does not recommend using transactions due to its poor performance.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">Tiered Storage</td></tr>

<tr>

Ignite provides tiered storage model where data can be stored and moved between

on-heap, off-heap, and swap space. Going up the tier

provides more data storage capacity, with gradual increase in latency.

</td>

Coherence does not have any support for tiered storage.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">Data Streaming</td></tr>

<tr>

Ignite provides support for in-memory streaming, including support for maintaining and

querying sliding windows of streaming data.

</td>

Coherence does not offer any support for streaming.

</td>

</tr>

<tr><td colspan="2" style="text-align: center">Configuration</td></tr>

<tr>

Ignite supports standard Java beans for configuration and natively integrates with

Spring XML, as well as provides ability to easily configure the system directly from code.

</td>

Coherence uses a proprietary XML format for configuration and does not

have any support for configuring a system directly from code.

</td>

</tr>

</tbody>

</table>

</section>

</main>

</div>

</body>

</html>