DBMS > Apache Impala vs. Drizzle vs. KairosDB vs. Microsoft SQL Server vs. RavenDB

System Properties Comparison Apache Impala vs. Drizzle vs. KairosDB vs. Microsoft SQL Server vs. RavenDB

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.

Description

Analytic DBMS for Hadoop

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Website

impala.apache.org

github.com/kairosdb/kairosdb

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

ravendb.net

Technical documentation

impala.apache.org/impala-docs.html

kairosdb.github.io

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

ravendb.net/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Drizzle project, originally started by Brian Aker

Microsoft

Hibernating Rhinos

Initial release

2013

2008

2013

1989

2010

Current release

4.1.0, June 2022

7.2.4, September 2012

1.2.2, November 2018

SQL Server 2022, November 2022

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

AGPL version 3, 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

C++

Java

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux
OS X
Windows

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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-like DML and DDL statements

yes

with proprietary extensions

yes

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

JDBC

Graphite protocol
HTTP REST
Telnet API

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java
JavaScript

Node.js
PHP
Python

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

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

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

selectable replication factor

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

yes, but depending on the SQL-Server Edition

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.