DBMS > Amazon Aurora vs. IBM Cloudant vs. Percona Server for MongoDB vs. Snowflake vs. TigerGraph

System Properties Comparison Amazon Aurora vs. IBM Cloudant vs. Percona Server for MongoDB vs. Snowflake vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Database as a Service offering based on Apache CouchDB

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

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Document store

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

aws.amazon.com/rds/aurora

www.ibm.com/products/cloudant

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

www.snowflake.com

www.tigergraph.com

Technical documentation

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

cloud.ibm.com/docs/Cloudant

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

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Amazon

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Percona

Snowflake Computing Inc.

Initial release

2015

2010

2015

2014

2017

Current release

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

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

C++

Server operating systems

hosted

Linux

hosted

Linux

Data scheme

yes

schema-free

yes

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GSQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

proprietary protocol using JSON

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON 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#
Java
JavaScript
Objective-C
PHP
Ruby

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

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

Access rights for users and roles

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

Role-based access control

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.