DBMS > Atos Standard Common Repository vs. Drizzle vs. eXtremeDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. eXtremeDB vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Natively in-memory DBMS with options for persistency, high-availability and clustering

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Key-value store

Relational DBMS

Relational DBMS
Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#100	Relational DBMS
	#18	Time Series DBMS

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

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.mcobject.com

azure.microsoft.com/services/cosmos-db

Technical documentation

www.mcobject.com/docs/extremedb.htm

learn.microsoft.com/azure/cosmos-db

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

McObject

Microsoft

Initial release

2016

2008

2001

2014

Current release

1703

7.2.4, September 2012

8.2, 2021

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

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

Java

C++

C and C++

Server operating systems

Linux

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
macOS
Solaris
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

JSON types

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

support of XML interfaces available

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

with proprietary extensions

yes

with the option: eXtremeSQL

SQL-like query language

APIs and other access methods

LDAP

JDBC

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

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

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

.Net
C
C#
C++
Java
Lua
Python
Scala

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

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

hooks for callbacks inside the server can be used.

yes

by defining events

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning / sharding

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

yes

Implicit feature of the cloud service

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

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

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

LDAP bind authentication

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights can be defined down to the item level

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.