DBMS > Amazon Aurora vs. Drizzle vs. GeoSpock vs. Microsoft Azure Cosmos DB

System Properties Comparison Amazon Aurora vs. Drizzle vs. GeoSpock vs. Microsoft Azure Cosmos DB

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.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

MySQL and PostgreSQL compatible cloud service by Amazon

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

Spatial and temporal data processing engine for extreme data scale

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Time Series DBMS

Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

aws.amazon.com/rds/aurora

geospock.com

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

Drizzle project, originally started by Brian Aker

GeoSpock

Microsoft

Initial release

2015

2008

2014

Current release

7.2.4, September 2012

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

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

Java, Javascript

Server operating systems

hosted

FreeBSD
Linux
OS X

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

temporal, categorical

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Java
PHP

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

hooks for callbacks inside the server can be used.

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Automatic sharding

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

Access rights can be defined down to the item level

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.