DBMS > BoltDB vs. Heroic vs. Microsoft Azure Cosmos DB vs. RocksDB vs. SiteWhere

System Properties Comparison BoltDB vs. Heroic vs. Microsoft Azure Cosmos DB vs. RocksDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Globally distributed, horizontally scalable, multi-model database service

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

M2M integration platform for persisting/querying time series data

Primary database model

Key-value store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

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

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/boltdb/bolt

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

Spotify

Microsoft

Facebook, Inc.

SiteWhere

Initial release

2013

2014

2013

2010

Current release

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

Common Public Attribution License Version 1.0

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

C++

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Linux
OS X
Windows

Data scheme

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

JSON types

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

via Elasticsearch

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

C++ API
Java API

HTTP REST

Supported programming languages

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

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 can be defined down to the item level

Users with fine-grained authorization concept

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.