DBMS > DataFS vs. Drizzle vs. TerarkDB

System Properties Comparison DataFS vs. Drizzle vs. TerarkDB

Please select another system to include it in the comparison.

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

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Object oriented DBMS

Relational DBMS

Key-value store

Secondary database models

Graph DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

newdatabase.com

github.com/bytedance/terarkdb

Technical documentation

dev.mobiland.com/Overview.xsp

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Mobiland AG

Drizzle project, originally started by Brian Aker

ByteDance, originally Terark

Initial release

2018

2008

2016

Current release

1.1.263, October 2022

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

restricted open source version available

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

Windows

FreeBSD
Linux
OS X

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

JDBC

C++ API
Java API

Supported programming languages

.Net
C
C#
C++
VB.Net

C
C++
Java
PHP

C++
Java

Server-side scripts

Stored procedures

Triggers

no, except callback-events from server when changes happened

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

Windows-Profile

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.