DBMS > IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Oracle NoSQL vs. Solr vs. Sphinx

System Properties Comparison IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Oracle NoSQL vs. Solr vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

A widely used distributed, scalable search engine based on Apache Lucene

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

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

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

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.oracle.com/database/nosql/technologies/nosql

solr.apache.org

sphinxsearch.com

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

docs.oracle.com/en/database/other-databases/nosql-database/index.html

solr.apache.org/resources.html

sphinxsearch.com/docs

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Oracle

Apache Software Foundation

Sphinx Technologies Inc.

Initial release

2010

2014

2011

2006

2001

Current release

24.1, May 2024

9.6.1, May 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

Apache Version 2

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

Erlang

Java

C++

Server operating systems

hosted

Linux
Solaris SPARC/x86

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

JSON types

optional

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements

Solr Parallel SQL Interface

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP/JSON API

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

RESTful HTTP API

Java API
RESTful HTTP/JSON API

Proprietary protocol

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

C
C#
Go
Java
JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

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

JavaScript

Java plugins

Triggers

yes

JavaScript

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

yes

Implicit feature of the cloud service

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

configurable

ACID within a storage node (=shard)

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

off heap cache

yes

User concepts

Access control

Access rights for users can be defined per database

Access rights can be defined down to the item level

Access rights for users and roles

yes

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.