DBMS > Amazon Aurora vs. EXASOL vs. FatDB vs. Snowflake vs. Sphinx

System Properties Comparison Amazon Aurora vs. EXASOL vs. FatDB vs. Snowflake vs. Sphinx

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Search engine

Secondary database models

Document store

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

Score	8.50
Rank	#49	Overall
	#31	Relational DBMS

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

aws.amazon.com/rds/aurora

www.exasol.com

www.snowflake.com

sphinxsearch.com

Technical documentation

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

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Amazon

Exasol

FatCloud

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2015

2000

2012

2014

2001

Current release

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

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

Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

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

full-text index on all search fields

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

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

CLI Client
JDBC
ODBC

Proprietary protocol

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

Java
Lua
Python
R

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

user defined functions

yes

via applications

user defined functions

Triggers

yes

via applications

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

Access rights for users, groups and roles according to SQL-standard

Can implement custom security layer via applications

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.