use-cases/compare/redis.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 Redis</title>

</head>

<body>

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

<p>

Both, Apache Ignite and Redis provide distributed caching functionality, but the features supported

by either product are very different. Redis is mainly a data structure store, while Ignite fabric

provides many in-memory distributed components including data grid, compute grid,

streaming, and also data structures.

</p>

<p>

Given that Ignite is an in-memory data fabric and offers more functionality, a complete

feature-by-feature comparison is not really relevant, while we can still compare some

individual data grid features.

</p>

</section>

<thead>

<tr>

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

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

</tr>

</thead>

<tbody>

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

<tr>

<p>

Ignite is fully compliant with <i><nobr>JCache (JSR 107)</nobr></i> specification for caching.

</p>

</td>

<p>

Redis does not implement <i><nobr>JCache (JSR 107)</nobr></i> specification for caching.

</p>

</td>

</tr>

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

<tr>

<p>

Ignite has full support for ACID transactions, including OPTIMISTIC and PESSIMISTIC

concurrency modes, as well as READ_COMMITTED, REPEATABLE_READ, and SERIALIZABLE isolation

levels.

</p>

</td>

<p>

Redis provides very limited support for client-side OPTIMISTIC transactions.

In case of concurrent update, clients are required to manually retry a transaction.

</p>

</td>

</tr>

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

<tr>

<p>

Ignite supports <i>PARTITIONED</i> caches which is similar to a distributed hash map

with every node in the cluster responsible only for a portion of the data.

Ignite will automatically rebalance the data in case of topology changes.

</p>

</td>

<p>

Redis does not provide partitioning, but it provides sharding with replicas.

Working with shards is more rigid and almost always requires a set of fairly involved

manual steps on both, clients and servers, every time a topology changes.

</p>

</td>

</tr>

<tr><td colspan="2" style="text-align: center"><b>Full Replication</b></td></tr>

<tr>

<p>

Ignite has support for <i>REPLICATED</i> caches where every key-value pair is

replicated on every node in the cluster.

</td>

<p>

Redis does not have direct support for full replication.

</p>

</td>

</tr>

<tr><td colspan="2" style="text-align: center"><b>Native Objects</b></td></tr>

<tr>

<p>

Ignite allows users to use their own domain object model and provides native support

for any Java/Scala, C++, and .NET/C# data types (objects). Users are free to store any

application and domain object in Ignite caches.

</p>

</td>

<p>

Redis does not allow users to work with their own data types and only supports the

predefined set of primitive data structures, such as sets, lists, arrays, and some others.

</p>

</td>

</tr>

<tr><td colspan="2" style="text-align: center"><b>Client-side (Near) Caching</b></td></tr>

<tr>

<p>

Ignite provides direct support for client-side caching for most recently accessed data.

</p>

</td>

<p>

Redis does not provide support for client-side caching.

</p>

</td>

</tr>

<tr><td colspan="2" style="text-align: center"><b>Collocated (server-side) Processing</b></td></tr>

<tr>

<p>

Ignite allows executing any native Java, C++, and .NET/C# code directly on the server-side,

close to the data, in collocated fashion.

</p>

</td>

<p>

Redis generally does not have any collocated processing and allows primitive server-side

code execution only with LUA scripting language. There is no direct support for Java,

.NET, or C++ on the server side.

</p>

</td>

</tr>

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

<tr>

<p>

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

</p>

</td>

<p>

Redis does not have any query language and only supports client-side caching API.

</p>

</td>

</tr>

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

<tr>

<p>

Ignite provides direct support for client-side and server-side continuous queries.

Users can setup server-side filters to reduce and narrow down the amount of events sent

to clients.

</p>

</td>

<p>

Redis provides support for client-side key-based event notifications. However, it does not

allow to provide server-side filters, hence causing a significant network traffic for

update notifications between servers and clients.

</p>

</td>

</tr>

<tr><td colspan="2" style="text-align: center"><b>Database Integration</b></td></tr>

<tr>

<p>

Ignite can automatically integrate with external databases - RDBMS, NoSQL, and HDFS.

</p>

</td>

<p>

Redis does not integrate with external databases.

</p>

</td>

</tr>

</tbody>

</table>

</section>

</main>

</div>

</body>

</html>