DBMS > Apache Druid vs. Microsoft SQL Server vs. Riak KV vs. STSdb

System Properties Comparison Apache Druid vs. Microsoft SQL Server vs. Riak KV vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Microsofts flagship relational DBMS

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

druid.apache.org

www.microsoft.com/en-us/sql-server

github.com/STSSoft/STSdb4

Technical documentation

druid.apache.org/docs/latest/design

learn.microsoft.com/en-US/sql/sql-server

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Apache Software Foundation and contributors

Microsoft

OpenSource, formerly Basho Technologies

STS Soft SC

Initial release

2012

1989

2009

2011

Current release

29.0.1, April 2024

SQL Server 2022, November 2022

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache license v2

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Erlang

Server operating systems

Linux
OS X
Unix

Linux
Windows

Linux
OS X

Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

restricted

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP API
Native Erlang Interface

.NET Client API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
Java

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes, but depending on the SQL-Server Edition

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

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

User concepts

Access control

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

fine grained access rights according to SQL-standard

yes, using Riak Security

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.