DBMS > IBM Cloudant vs. Microsoft Azure SQL Database vs. SQLite vs. SQream DB vs. VoltDB

System Properties Comparison IBM Cloudant vs. Microsoft Azure SQL Database vs. SQLite vs. SQream DB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used embeddable, in-process RDBMS

a GPU-based, columnar RDBMS for big data analytics workloads

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.ibm.com/products/cloudant

azure.microsoft.com/en-us/products/azure-sql/database

www.sqlite.org

sqream.com

www.voltdb.com

Technical documentation

cloud.ibm.com/docs/Cloudant

docs.microsoft.com/en-us/azure/azure-sql

www.sqlite.org/docs.html

docs.sqream.com

docs.voltdb.com

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Dwayne Richard Hipp

SQream Technologies

VoltDB Inc.

Initial release

2010

2000

2017

2010

Current release

V12

3.46.0 (23 May 2024), May 2024

2022.1.6, December 2022

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Public Domain

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

C++, CUDA, Haskell, Java, Scala

Java, C++

Server operating systems

hosted

server-less

Linux

Linux
OS X

for development

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, ANSI Standard SQL Types

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

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++
Java
JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Transact SQL

user defined functions in Python

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal and vertical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, with always 3 replicas available

none

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

atomic operations within a document possible

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.