DBMS > Apache Druid vs. HarperDB vs. Microsoft SQL Server vs. Rockset

System Properties Comparison Apache Druid vs. HarperDB vs. Microsoft SQL Server vs. Rockset

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Microsofts flagship relational DBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS
Search engine

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	0.55
Rank	#248	Overall
	#38	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

druid.apache.org

www.harperdb.io

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

rockset.com

Technical documentation

druid.apache.org/docs/latest/design

docs.harperdb.io/docs

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

docs.rockset.com

Developer

Apache Software Foundation and contributors

HarperDB

Microsoft

Rockset

Initial release

2012

2017

1989

2019

Current release

29.0.1, April 2024

3.1, August 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache license v2

commercial

free community edition available

commercial

restricted free version is available

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

Java

Node.js

C++

Server operating systems

Linux
OS X
Unix

Linux
OS X

Linux
Windows

hosted

Data scheme

yes

schema-less columns are supported

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL for querying

SQL-like data manipulation statements

yes

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

A table resides as a whole on one (or more) nodes in a cluster

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

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

the nodes on which a table resides can be defined

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

fine grained access rights according to SQL-standard

Access rights for users and organizations can be defined via Rockset console

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.