DBMS > Badger vs. Heroic vs. LevelDB vs. Microsoft Azure Cosmos DB vs. SiteWhere

System Properties Comparison Badger vs. Heroic vs. LevelDB vs. Microsoft Azure Cosmos DB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Globally distributed, horizontally scalable, multi-model database service

M2M integration platform for persisting/querying time series data

Primary database model

Key-value store

Time Series DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

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

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/dgraph-io/badger

github.com/spotify/heroic

github.com/google/leveldb

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

Technical documentation

godoc.org/github.com/dgraph-io/badger

spotify.github.io/heroic

github.com/google/leveldb/blob/main/doc/index.md

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

Developer

DGraph Labs

Spotify

Google

Microsoft

SiteWhere

Initial release

2017

2014

2011

2014

2010

Current release

1.23, February 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

BSD

commercial

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

Illumos
Linux
OS X
Windows

hosted

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

HTTP REST

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

yes

Implicit feature of the cloud service

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

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

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

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.