DBMS > KeyDB vs. Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. Snowflake

System Properties Comparison KeyDB vs. Microsoft Azure SQL Database vs. NSDb vs. OrigoDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

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

Primary database model

Key-value store

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Relational 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	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/en-us/products/azure-sql/database

nsdb.io

origodb.com

www.snowflake.com

Technical documentation

docs.keydb.dev

docs.microsoft.com/en-us/azure/azure-sql

nsdb.io/Architecture

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

EQ Alpha Technology Ltd.

Microsoft

Robert Friberg et al

Snowflake Computing Inc.

Initial release

2019

2010

2017

2009

under the name LiveDB

2014

Current release

V12

License

Commercial or Open Source

Open Source

BSD-3

commercial

Open Source

Apache Version 2.0

Open Source

commercial

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

C++

Java, Scala

Server operating systems

Linux

hosted

Linux
macOS

Linux
Windows

hosted

Data scheme

schema-free

yes

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

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

yes: int, bigint, decimal, string

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

by using the Redis Search module

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
Scala

.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

Transact SQL

yes

user defined functions

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, with always 3 replicas available

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

depending on model

yes

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

Using Apache Lucene

yes

Write ahead log

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

simple password-based access control and ACL

fine grained access rights according to SQL-standard

Role based authorization

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.