DBMS > Drizzle vs. FatDB vs. RocksDB vs. Sequoiadb vs. TimescaleDB

System Properties Comparison Drizzle vs. FatDB vs. RocksDB vs. Sequoiadb vs. TimescaleDB

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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

NewSQL database with distributed OLTP and SQL

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Document store
Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

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

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

rocksdb.org

www.sequoiadb.com

www.timescale.com

Technical documentation

github.com/facebook/rocksdb/wiki

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.timescale.com

Developer

Drizzle project, originally started by Brian Aker

FatCloud

Facebook, Inc.

Sequoiadb Ltd.

Timescale

Initial release

2008

2012

2013

2017

Current release

7.2.4, September 2012

9.2.1, May 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

BSD

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache 2.0

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

Server operating systems

FreeBSD
Linux
OS X

Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

with proprietary extensions

Via inetgration in SQL Server

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

C++ API
Java API

proprietary protocol using JSON

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C
C++
Java
PHP

C
C++
Go
Java
Perl
Python
Ruby

.Net
C++
Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

yes

Source-replica replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
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

yes

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

simple password-based access control

fine grained access rights according to SQL-standard

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.