DBMS > Apache Impala vs. Derby vs. Drizzle vs. PouchDB vs. RocksDB

System Properties Comparison Apache Impala vs. Derby vs. Drizzle vs. PouchDB vs. RocksDB

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

JavaScript DBMS with an API inspired by CouchDB

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Document store

Key-value store

Secondary database models

Document store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

impala.apache.org/impala-docs.html

db.apache.org/derby/manuals/index.html

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Apache Software Foundation

Facebook, Inc.

Initial release

2013

1997

2008

2012

2013

Current release

4.1.0, June 2022

10.17.1.0, November 2023

7.2.4, September 2012

7.1.1, June 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

Open Source

GNU GPL

Open Source

BSD

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

JavaScript

C++

Server operating systems

Linux

All OS with a Java VM

FreeBSD
Linux
OS X

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

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

via views

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

Java

C
C++
Java
PHP

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Java Stored Procedures

View functions in JavaScript

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.