DBMS > Apache Druid vs. HEAVY.AI vs. Rockset vs. SQLite

System Properties Comparison Apache Druid vs. HEAVY.AI vs. Rockset vs. SQLite

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

Relational DBMS
Search engine

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

Score	2.85
Rank	#96	Overall
	#50	Relational DBMS
	#6	Time Series DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

druid.apache.org

github.com/heavyai/heavydb
www.heavy.ai

rockset.com

www.sqlite.org

Technical documentation

druid.apache.org/docs/latest/design

docs.heavy.ai

docs.rockset.com

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

HEAVY.AI, Inc.

Rockset

Dwayne Richard Hipp

Initial release

2012

2016

2019

2000

Current release

30.0.0, June 2024

5.10, January 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

Public Domain

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

C++ and CUDA

C++

Server operating systems

Linux
OS X
Unix

Linux

hosted

server-less

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

dynamic typing

yes

not rigid because of 'dynamic typing' concept.

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.

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

yes

Read-only SQL queries, including JOINs

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages supporting JDBC/ODBC/Thrift
Python

Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Round robin

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication

yes

none

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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.