DBMS > BoltDB vs. GeoSpock vs. Heroic vs. IBM Cloudant vs. RocksDB

System Properties Comparison BoltDB vs. GeoSpock vs. Heroic vs. IBM Cloudant vs. RocksDB

Editorial information provided by DB-Engines

Name

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

Description

An embedded key-value store for Go.

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

Database as a Service offering based on Apache CouchDB

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

Primary database model

Secondary database models

Time Series DBMS

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

Score	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

geospock.com

github.com/spotify/heroic

www.ibm.com/products/cloudant

rocksdb.org

Technical documentation

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

github.com/facebook/rocksdb/wiki

Developer

GeoSpock

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Facebook, Inc.

Initial release

2013

2014

2010

2013

Current release

2.0, September 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache 2.0

commercial

Open Source

BSD

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

Erlang

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

yes

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

temporal, categorical

yes

via Elasticsearch

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

APIs and other access methods

JDBC

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

RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

atomic operations within a document possible

yes

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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 can be defined per database

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.