DBMS > Dgraph vs. Drizzle vs. KairosDB vs. Microsoft SQL Server vs. ToroDB

System Properties Comparison Dgraph vs. Drizzle vs. KairosDB vs. Microsoft SQL Server vs. ToroDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed and scalable native Graph DBMS

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Distributed Time Series DBMS based on Cassandra or H2

Microsofts flagship relational DBMS

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

dgraph.io

github.com/kairosdb/kairosdb

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

github.com/torodb/server

Technical documentation

dgraph.io/docs

kairosdb.github.io

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

Developer

Dgraph Labs, Inc.

Drizzle project, originally started by Brian Aker

Microsoft

8Kdata

Initial release

2016

2008

2013

1989

2016

Current release

7.2.4, September 2012

1.2.2, November 2018

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GNU GPL

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

AGPL-V3

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++

Java

C++

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux
OS X
Windows

Linux
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

with proprietary extensions

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC

Graphite protocol
HTTP REST
Telnet API

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

Supported programming languages

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

C
C++
Java
PHP

Java
JavaScript

Node.js
PHP
Python

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

Server-side scripts

Stored procedures

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

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

based on Cassandra

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

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

Planned for future releases

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.