DBMS > Amazon Aurora vs. CouchDB vs. GeoMesa vs. KairosDB vs. Snowflake

System Properties Comparison Amazon Aurora vs. CouchDB vs. GeoMesa vs. KairosDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Distributed Time Series DBMS based on Cassandra or H2

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

aws.amazon.com/rds/aurora

couchdb.apache.org

www.geomesa.org

github.com/kairosdb/kairosdb

www.snowflake.com

Technical documentation

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

docs.couchdb.org/en/stable

www.geomesa.org/documentation/stable/user/index.html

kairosdb.github.io

docs.snowflake.net/manuals/index.html

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

CCRi and others

Snowflake Computing Inc.

Initial release

2015

2005

2014

2013

2014

Current release

3.3.3, December 2023

5.0.0, May 2024

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

Erlang

Scala

Java

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

Graphite protocol
HTTP REST
Telnet API

CLI Client
JDBC
ODBC

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#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java
JavaScript

Node.js
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

improved architecture with release 2.0

depending on storage layer

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

depending on storage layer

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

yes

depending on the DBMS used for storage

simple password-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.