DBMS > Amazon DynamoDB vs. Drizzle vs. EsgynDB vs. gStore vs. OrigoDB

System Properties Comparison Amazon DynamoDB vs. Drizzle vs. EsgynDB vs. gStore vs. OrigoDB

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

A native Graph DBMS to store and maintain very large RDF datasets.

A fully ACID in-memory object graph database

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS
RDF store

Document store
Object oriented DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

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

Website

aws.amazon.com/dynamodb

www.esgyn.cn

en.gstore.cn

origodb.com

Technical documentation

docs.aws.amazon.com/dynamodb

en.gstore.cn/#/enDocs

origodb.com/docs

Developer

Amazon

Drizzle project, originally started by Brian Aker

Esgyn

Robert Friberg et al

Initial release

2012

2008

2015

2016

2009

under the name LiveDB

Current release

7.2.4, September 2012

1.2, November 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GNU GPL

commercial

Open Source

BSD

Open Source

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++, Java

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux

Linux
Windows

Data scheme

schema-free

yes

schema-free and OWL/RDFS-schema support

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP API

JDBC

ADO.NET
JDBC
ODBC

HTTP API
SPARQL 1.1

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

C++
Java
JavaScript (Node.js)
PHP
Python

.Net

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Users, roles and permissions, Role-Based Access Control (RBAC) supported

Role based authorization

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.