DBMS > CouchDB vs. Graphite vs. OrigoDB vs. QuestDB vs. RocksDB

System Properties Comparison CouchDB vs. Graphite vs. OrigoDB vs. QuestDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A fully ACID in-memory object graph database

A high performance open source SQL database for time series data

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

Primary database model

Document store

Time Series DBMS

Document store
Object oriented DBMS

Time Series DBMS

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

Relational DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	2.70
Rank	#105	Overall
	#8	Time Series DBMS

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

Website

couchdb.apache.org

github.com/graphite-project/graphite-web

origodb.com

questdb.io

rocksdb.org

Technical documentation

docs.couchdb.org/en/stable

graphite.readthedocs.io

origodb.com/docs

questdb.io/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

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

Chris Davis

Robert Friberg et al

QuestDB Technology Inc

Facebook, Inc.

Initial release

2005

2006

2009

under the name LiveDB

2014

2013

Current release

3.3.3, December 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

Apache 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

Erlang

Python

Java (Zero-GC), C++, Rust

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
Unix

Linux
Windows

Linux
macOS
Windows

Linux

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

schema-free

Typing

predefined data types such as float or date

Numeric data only

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL with time-series extensions

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Sockets

.NET Client API
HTTP API
LINQ

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

C++ API
Java API

Supported programming languages

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

JavaScript (Node.js)
Python

.Net

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning (by timestamps)

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

Source-replica replication with eventual consistency

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

atomic operations within a single document possible

ACID

ACID for single-table writes

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

locking

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

through memory mapped files

yes

User concepts

Access control

Access rights for users can be defined per database

Role based authorization

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Fluid real-time dashboards with Grafana and QuestDB
11 June 2024

QuestDB 8.0: Major Release
23 May 2024

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

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.