DBMS > IBM Cloudant vs. IRONdb vs. Microsoft SQL Server vs. Sphinx

System Properties Comparison IBM Cloudant vs. IRONdb vs. Microsoft SQL Server vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Database as a Service offering based on Apache CouchDB

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Microsofts flagship relational DBMS

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

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.ibm.com/products/cloudant

www.circonus.com/solutions/time-series-database/

www.microsoft.com/en-us/sql-server

sphinxsearch.com

Technical documentation

cloud.ibm.com/docs/Cloudant

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/en-US/sql/sql-server

sphinxsearch.com/docs

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Circonus LLC.

Microsoft

Sphinx Technologies Inc.

Initial release

2010

2017

1989

2001

Current release

V0.10.20, January 2018

SQL Server 2022, November 2022

3.5.1, February 2023

License

Commercial or Open Source

commercial

restricted free version is 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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Erlang

C and C++

C++

Server operating systems

hosted

Linux

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Proprietary protocol

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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, in Lua

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

tables can be distributed across several files (horizontal partitioning); sharding through federation

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

configurable replication factor, datacenter aware

yes, but depending on the SQL-Server Edition

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 per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

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

User concepts

Access control

Access rights for users can be defined per database

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.