DBMS > Microsoft Azure Cosmos DB vs. OrigoDB vs. SpatiaLite vs. VoltDB

System Properties Comparison Microsoft Azure Cosmos DB vs. OrigoDB vs. SpatiaLite vs. VoltDB

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

A fully ACID in-memory object graph database

Spatial extension of SQLite

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
Graph DBMS
Key-value store
Wide column store

Document store
Object oriented DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Relational 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	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	1.72
Rank	#149	Overall
	#3	Spatial DBMS

Score	1.46
Rank	#159	Overall
	#74	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

www.voltdb.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

origodb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

docs.voltdb.com

Developer

Microsoft

Robert Friberg et al

Alessandro Furieri

VoltDB Inc.

Initial release

2014

2009

under the name LiveDB

2008

2010

Current release

5.0.0, August 2020

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C++

Java, C++

Server operating systems

hosted

Linux
Windows

server-less

Linux
OS X

for development

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

Java

Triggers

JavaScript

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

none

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

depending on model

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.