DBMS > Drizzle vs. EsgynDB vs. Memcached vs. VoltDB

System Properties Comparison Drizzle vs. EsgynDB vs. Memcached 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

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

In-memory key-value store, originally intended for caching

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

Relational DBMS

Key-value store

Relational DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.esgyn.cn

www.memcached.org

www.voltdb.com

Technical documentation

github.com/memcached/memcached/wiki

docs.voltdb.com

Developer

Drizzle project, originally started by Brian Aker

Esgyn

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

VoltDB Inc.

Initial release

2008

2015

2003

2010

Current release

7.2.4, September 2012

1.6.27, May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

BSD license

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

FreeBSD
Linux
OS X

Linux

FreeBSD
Linux
OS X
Unix
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

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

JDBC

ADO.NET
JDBC
ODBC

Proprietary protocol

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

Java

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

none

Repcached, a Memcached patch, provides this functionallity

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

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

Redis extends the lead in the DB-Engines key-value store ranking
3 February 2014, Matthias Gelbmann

New DB-Engines Ranking shows the popularity of database management systems
3 October 2012, Matthias Gelbmann, Paul Andlinger

show all

Recent citations in the news

Memcached Adoption Spurs Solutions
30 May 2024, Data Center Knowledge

Why DDoS Threat Actors Are Shifting Their Tactics
15 March 2024, Infosecurity Magazine

Ubuntu 24.04 Helping Achieve Greater Performance On Intel Xeon Scalable Emerald Rapids
8 March 2024, Phoronix

Why Redis beats Memcached for caching
14 September 2017, InfoWorld

What are memcached servers, and why are they being used to launch record-setting DDoS attacks?
6 March 2018, GeekWire

provided by Google News

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

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

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page