DBMS > GeoSpock vs. Heroic vs. Oracle Berkeley DB vs. RocksDB vs. ToroDB

System Properties Comparison GeoSpock vs. Heroic vs. Oracle Berkeley DB vs. RocksDB vs. ToroDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used in-process key-value store

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Document store

Secondary database models

Time Series DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

geospock.com

github.com/spotify/heroic

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

github.com/torodb/server

Technical documentation

spotify.github.io/heroic

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

Developer

GeoSpock

Spotify

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

8Kdata

Initial release

2014

1994

2013

2016

Current release

2.0, September 2019

18.1.40, May 2020

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

BSD

Open Source

AGPL-V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java, Javascript

Java

C, Java, C++ (depending on the Berkeley DB edition)

C++

Java

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

only with the Berkeley DB XML edition

Secondary indexes

temporal, categorical

yes

via Elasticsearch

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

Supported programming languages

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

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 for users can be defined per table

Access rights for users and roles

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.