DBMS > Amazon DynamoDB vs. Drizzle vs. Google Cloud Datastore vs. OpenEdge vs. Percona Server for MongoDB

System Properties Comparison Amazon DynamoDB vs. Drizzle vs. Google Cloud Datastore vs. OpenEdge vs. Percona Server for MongoDB

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Application development environment with integrated database management system

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Document store
Key-value store

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

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

aws.amazon.com/dynamodb

cloud.google.com/datastore

www.progress.com/openedge

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

documentation.progress.com/output/ua/OpenEdge_latest

docs.percona.com/percona-distribution-for-mongodb

Developer

Amazon

Drizzle project, originally started by Brian Aker

Google

Progress Software Corporation

Percona

Initial release

2012

2008

1984

2015

Current release

7.2.4, September 2012

OpenEdge 12.2, March 2020

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GNU GPL

commercial

Open Source

GPL Version 2

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

Server operating systems

hosted

FreeBSD
Linux
OS X

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (GQL)

yes

close to SQL 92

APIs and other access methods

RESTful HTTP API

JDBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Java
PHP

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

using Google App Engine

yes

JavaScript

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

via In-Memory Engine

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users and groups

Access rights for users and roles

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.