DBMS > Geode vs. GigaSpaces vs. RocksDB vs. searchxml

System Properties Comparison Geode vs. GigaSpaces vs. RocksDB vs. searchxml

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Key-value store

Native XML DBMS
Search engine

Secondary database models

Graph DBMS
Search engine

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

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

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

geode.apache.org

www.gigaspaces.com

rocksdb.org

www.searchxml.net/category/products

Technical documentation

geode.apache.org/docs

docs.gigaspaces.com/latest/landing.html

github.com/facebook/rocksdb/wiki

www.searchxml.net/support/handouts

Developer

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

Gigaspaces Technologies

Facebook, Inc.

informationpartners gmbh

Initial release

2002

2000

2013

2015

Current release

1.1, February 2017

15.5, September 2020

8.11.4, April 2024

1.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; Commercial licenses available

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

Java, C++, .Net

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Solaris
Windows

Linux

Windows

Data scheme

schema-free

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.

XML can be used for describing objects metadata

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-99 for query and DML statements

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

C++ API
Java API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

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

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

Triggers

yes

Cache Event Listeners

yes, event driven architecture

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

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

ACID

yes

multiple readers, single writer

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

Role-based access control

Domain, group and role-based access control at the document level and for application services

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.