DBMS > Microsoft Azure Cosmos DB vs. mSQL vs. Oracle Berkeley DB vs. Warp 10

System Properties Comparison Microsoft Azure Cosmos DB vs. mSQL vs. Oracle Berkeley DB vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used in-process key-value store

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Secondary database models

Spatial DBMS

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

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

Score	1.67
Rank	#151	Overall
	#70	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

azure.microsoft.com/services/cosmos-db

hughestech.com.au/products/msql

www.oracle.com/database/technologies/related/berkeleydb.html

www.warp10.io

Technical documentation

learn.microsoft.com/azure/cosmos-db

docs.oracle.com/cd/E17076_05/html/index.html

www.warp10.io/content/02_Getting_started

Developer

Microsoft

Hughes Technologies

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SenX

Initial release

2014

1994

2015

Current release

4.4, October 2021

18.1.40, May 2020

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

commercial license available

Open Source

Apache License 2.0

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

C, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON 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

only with the Berkeley DB XML edition

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

JavaScript

yes

WarpScript

Triggers

JavaScript

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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 can be defined down to the item level

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.