DBMS > Apache Druid vs. Atos Standard Common Repository vs. Badger vs. Snowflake vs. Tkrzw

System Properties Comparison Apache Druid vs. Atos Standard Common Repository vs. Badger vs. Snowflake vs. Tkrzw

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Cloud-based data warehousing service for structured and semi-structured data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS
Time Series DBMS

Document store
Key-value store

Key-value store

Relational DBMS

Key-value store

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

druid.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/dgraph-io/badger

www.snowflake.com

dbmx.net/tkrzw

Technical documentation

druid.apache.org/docs/latest/design

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

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation and contributors

Atos Convergence Creators

DGraph Labs

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2012

2016

2017

2014

2020

Current release

29.0.1, April 2024

1703

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.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++

Server operating systems

Linux
OS X
Unix

Linux

BSD
Linux
OS X
Solaris
Windows

hosted

Linux
macOS

Data scheme

yes

schema-less columns are supported

Schema and schema-less with LDAP views

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

LDAP

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages with LDAP bindings

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

cell division

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

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

using specific database classes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

LDAP bind authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

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.