DBMS > Apache Impala vs. CouchDB vs. HugeGraph vs. RocksDB

System Properties Comparison Apache Impala vs. CouchDB vs. HugeGraph vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A fast-speed and highly-scalable Graph DBMS

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

Primary database model

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

impala.apache.org

couchdb.apache.org

github.com/hugegraph
hugegraph.apache.org

rocksdb.org

Technical documentation

impala.apache.org/impala-docs.html

docs.couchdb.org/en/stable

hugegraph.apache.org/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Baidu

Facebook, Inc.

Initial release

2013

2005

2018

2013

Current release

4.1.0, June 2022

3.3.3, December 2023

0.9

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

Open Source

Apache Version 2.0

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

Erlang

Java

C++

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Unix

Linux

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.

Secondary indexes

yes

via views

yes

also supports composite index and range index

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

Java API
RESTful HTTP API
TinkerPop Gremlin

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Groovy
Java
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions in JavaScript

asynchronous Gremlin script jobs

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

yes

depending on used storage backend, e.g. Cassandra and HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

atomic operations within a single document possible

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

Users, roles and permissions

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.