DBMS > Microsoft Azure Cosmos DB vs. Oracle Berkeley DB vs. OrigoDB vs. Solr vs. Stardog

System Properties Comparison Microsoft Azure Cosmos DB vs. Oracle Berkeley DB vs. OrigoDB vs. Solr vs. Stardog

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

Widely used in-process key-value store

A fully ACID in-memory object graph database

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Object oriented DBMS

Search engine

Graph DBMS
RDF store

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	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Score	2.05
Rank	#129	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

azure.microsoft.com/services/cosmos-db

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

origodb.com

solr.apache.org

www.stardog.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

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

origodb.com/docs

solr.apache.org/resources.html

docs.stardog.com

Developer

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Robert Friberg et al

Apache Software Foundation

Stardog-Union

Initial release

2014

1994

2009

under the name LiveDB

2006

2010

Current release

18.1.40, May 2020

9.5.0, February 2024

7.3.0, May 2020

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Apache Version 2

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Windows

All OS with a Java VM

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

Linux
macOS
Windows

Data scheme

schema-free

yes

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

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

yes

JSON types

User defined using .NET types and collections

yes

supports customizable data types and automatic typing

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

can be achieved using .NET

yes

Import/export of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

yes

All search fields are automatically indexed

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language

yes

SQL interfaced based on SQLite is available

Solr Parallel SQL Interface

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

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
RESTful HTTP/JSON API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

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

.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

.Net

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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

yes

Java plugins

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

JavaScript

yes

only for the SQL API

yes

Domain Events

yes

User configurable commands triggered on index changes

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

yes

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

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

Eventual Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

depending on model

yes

relationships in graphs

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

yes

Access rights for users and roles

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.