DBMS > Amazon Aurora vs. Faircom EDGE vs. FatDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Amazon Aurora vs. Faircom EDGE vs. FatDB vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

MySQL and PostgreSQL compatible cloud service by Amazon

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Spatial DBMS

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

Score	7.84
Rank	#44	Overall
	#28	Relational DBMS

Score	0.02
Rank	#370	Overall
	#55	Key-value stores
	#157	Relational DBMS

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

Website

aws.amazon.com/rds/aurora

www.faircom.com/products/faircom-edge

azure.microsoft.com/services/cosmos-db

Technical documentation

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

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

FairCom Corporation

FatCloud

Microsoft

Initial release

2015

1979

2012

2014

Current release

V3, October 2020

License

Commercial or Open Source

commercial

Restricted, free version available

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

ANSI C, C++

Server operating systems

hosted

Android
Linux

ARM, x86
Raspbian
Windows

Windows

hosted

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

ANSI SQL queries

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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#
C++
Java
JavaScript
PHP
Python
VB.Net

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

via applications

JavaScript

Triggers

yes

via applications

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

File partitioning

Customizable business rules for partitioning

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

when using SQL

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

across SQL and NoSQL

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

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Can implement custom security layer via applications

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.