DBMS > DataFS vs. Drizzle vs. EsgynDB vs. VoltDB

System Properties Comparison DataFS vs. Drizzle vs. EsgynDB vs. VoltDB

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Object oriented DBMS

Relational DBMS

Secondary database models

Graph DBMS

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

Score	0.02
Rank	#369	Overall
	#18	Object oriented DBMS

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

newdatabase.com

www.esgyn.cn

www.voltdb.com

Technical documentation

dev.mobiland.com/Overview.xsp

docs.voltdb.com

Developer

Mobiland AG

Drizzle project, originally started by Brian Aker

Esgyn

VoltDB Inc.

Initial release

2018

2008

2015

2010

Current release

1.1.263, October 2022

7.2.4, September 2012

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++, Java

Java, C++

Server operating systems

Windows

FreeBSD
Linux
OS X

Linux

Linux
OS X

for development

Data scheme

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

yes

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

yes

only a subset of SQL 99

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

JDBC

ADO.NET
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C#
C++
VB.Net

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

Java

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

Windows-Profile

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

Unveiling Volt Active Data’s game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Announces Key New Hires
26 October 2021, citybiz

VoltDB Aims for Fast Big Data Development
29 January 2015, ADT Magazine

Solutions Review Sits Down with VoltDB CEO David Flower
17 April 2018, Solutions Review

provided by Google News

Share this page