DBMS > KeyDB vs. Microsoft SQL Server vs. Quasardb vs. Riak KV vs. SiteWhere

System Properties Comparison KeyDB vs. Microsoft SQL Server vs. Quasardb vs. Riak KV vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Microsofts flagship relational DBMS

Distributed, high-performance timeseries database

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

Primary database model

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

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

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

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

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

quasar.ai

github.com/sitewhere/sitewhere

Technical documentation

docs.keydb.dev

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

doc.quasar.ai/master

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

sitewhere1.sitewhere.io/index.html

Developer

EQ Alpha Technology Ltd.

Microsoft

quasardb

OpenSource, formerly Basho Technologies

SiteWhere

Initial release

2019

1989

2009

2010

Current release

SQL Server 2022, November 2022

3.14.1, January 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

BSD-3

commercial

restricted free version is available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

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

C++

Erlang

Java

Server operating systems

Linux

Linux
Windows

BSD
Linux
OS X
Windows

Linux
OS X

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

integer and binary

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

by using the Redis Search module

yes

with tags

restricted

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

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

HTTP API

HTTP API
Native Erlang Interface

HTTP REST

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

Server-side scripts

Stored procedures

Lua

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

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

Sharding

consistent hashing

Sharding

no "single point of failure"

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

Source-replica replication with selectable replication factor

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Eventual Consistency

Immediate 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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

simple password-based access control and ACL

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

yes, using Riak Security

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.