DBMS > IBM Cloudant vs. MySQL vs. Postgres-XL vs. Sphinx

System Properties Comparison IBM Cloudant vs. MySQL vs. Postgres-XL vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Widely used open source RDBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.ibm.com/products/cloudant

www.mysql.com

www.postgres-xl.org

sphinxsearch.com

Technical documentation

cloud.ibm.com/docs/Cloudant

dev.mysql.com/doc

www.postgres-xl.org/documentation

sphinxsearch.com/docs

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

since 2010, originally MySQL AB, then Sun

Sphinx Technologies Inc.

Initial release

2010

1995

2014

since 2012, originally named StormDB

2001

Current release

8.4.0, April 2024

10 R1, October 2018

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

Mozilla public license

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

Erlang

C and C++

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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

XML type, but no XML query functionality

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

yes

distributed, parallel query execution

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Proprietary protocol

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

atomic operations within a document possible

ACID

not for MyISAM storage engine

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.