DBMS > BigObject vs. Elasticsearch vs. Geode vs. RocksDB

System Properties Comparison BigObject vs. Elasticsearch vs. Geode vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Search engine

Key-value store

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

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

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

Website

bigobject.io

www.elastic.co/elasticsearch

geode.apache.org

rocksdb.org

Technical documentation

docs.bigobject.io

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

geode.apache.org/docs

github.com/facebook/rocksdb/wiki

Developer

BigObject, Inc.

Elastic

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

Facebook, Inc.

Initial release

2015

2010

2002

2013

Current release

8.6, January 2023

1.1, February 2017

8.11.4, April 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Elastic License

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD

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

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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.

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

SQL-like query language (OQL)

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

Java API
RESTful HTTP/JSON API

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

Transaction concepts

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

yes, on a single node

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

Memcached and Redis integration

yes

User concepts

Access control

Access rights per client and object definable

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.