DBMS > Amazon CloudSearch vs. Amazon DocumentDB vs. MySQL vs. Sphinx

System Properties Comparison Amazon CloudSearch vs. Amazon DocumentDB vs. MySQL vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Widely used open source RDBMS

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

Primary database model

Search engine

Document store

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/cloudsearch

aws.amazon.com/documentdb

www.mysql.com

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/cloudsearch

aws.amazon.com/documentdb/resources

dev.mysql.com/doc

sphinxsearch.com/docs

Developer

Amazon

Oracle

since 2010, originally MySQL AB, then Sun

Sphinx Technologies Inc.

Initial release

2012

2019

1995

2001

Current release

8.4.0, April 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

all search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (SphinxQL)

APIs and other access methods

HTTP API

proprietary protocol using JSON (MongoDB compatible)

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-document operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

authentication via encrypted signatures

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

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.