DBMS > Apache Druid vs. Hive vs. LevelDB vs. SQLite

System Properties Comparison Apache Druid vs. Hive vs. LevelDB 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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

Relational DBMS

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	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

druid.apache.org

hive.apache.org

github.com/google/leveldb

www.sqlite.org

Technical documentation

druid.apache.org/docs/latest/design

cwiki.apache.org/confluence/display/Hive/Home

github.com/google/leveldb/blob/main/doc/index.md

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

Apache Software Foundation

initially developed by Facebook

Google

Dwayne Richard Hipp

Initial release

2012

2011

2000

Current release

29.0.1, April 2024

3.1.3, April 2022

1.23, February 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2

Open Source

BSD

Open Source

Public Domain

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

Java

C++

Server operating systems

Linux
OS X
Unix

All OS with a Java VM

Illumos
Linux
OS X
Windows

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

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.

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
ODBC
Thrift

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C++
Java
PHP
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

yes

user defined functions and integration of map-reduce

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

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

via file-system locks

Durability

Support for making data persistent

yes

with automatic compression on writes

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, groups 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.