DBMS > Geode vs. Ignite vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison Geode vs. Ignite vs. RocksDB vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Key-value store

Key-value store
Relational DBMS

Key-value store

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

geode.apache.org

ignite.apache.org

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

geode.apache.org/docs

apacheignite.readme.io/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Apache Software Foundation

Facebook, Inc.

SAP

formerly Sybase

Initial release

2002

2015

2013

1992

Current release

1.1, February 2017

Apache Ignite 2.6

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++, Java, .Net

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes, on a single node

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights per client and object definable

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.