use-cases/compare/gemfire.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 Gemfire</title>

</head>

<body>

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

Both, Apache Ignite and Pivotal Gemfire 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 Gemfire 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">Gemfire</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>

Gemfire is a proprietary Pivotal software.

</td>

</tr>

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

<tr>

Ignite data grid is an implementation of JCache (JSR 107) specification.

JCache provides a very simple to use, but yet very powerful API for data access.

</td>

Gemfire does not implement JCache (JSR 107) and uses proprietary APIs.

</td>

</tr>

<tr>

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

depending on user configuration.

</td>

Gemfire does not offer any support for storing data off-heap.

</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>

Gemfire does not support the standard SQL syntax. Instead it comes with its own

object query language, called OQL.

</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>

Gemfire does not have any support for JOIN queries across caches or regions.

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

</td>

</tr>

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

<tr>

Ignite supports cross-partition transactions where transactions can be performed on

all partitions of a cache across the whole cluster.

</td>

Gemfire does not support transactions across multiple cache partitions or nodes.

</td>

</tr>

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

<tr>

Apache 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>

Gemfire 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>

Gemfire 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>

Gemfire uses a proprietary XML format for configuration and does not

have any support for configuring a system directly from code.

</td>

</tr>

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

<tr>

Ignite nodes are peers and automatically join the cluster on startup (without any

locator servers).

</td>

Gemfire requires a locator service to be started and maintained in order for

nodes to join or leave the cluster.

</td>

</tr>

</tbody>

</table>

</section>

</main>

</div>

</body>

</html>