DBMS > Amazon Aurora vs. Microsoft Azure Cosmos DB vs. Sphinx vs. TerarkDB

System Properties Comparison Amazon Aurora vs. Microsoft Azure Cosmos DB vs. Sphinx vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Globally distributed, horizontally scalable, multi-model database service

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Key-value 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	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	5.97
Rank	#56	Overall
	#5	Search engines

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

aws.amazon.com/rds/aurora

azure.microsoft.com/services/cosmos-db

sphinxsearch.com

github.com/bytedance/terarkdb

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

sphinxsearch.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon

Microsoft

Sphinx Technologies Inc.

ByteDance, originally Terark

Initial release

2015

2014

2001

2016

Current release

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

commercial

restricted open source version 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

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

All properties auto-indexed by default

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

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

Proprietary protocol

C++ API
Java 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

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Implicit feature of the cloud service

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

none

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

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

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

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.