DBMS > ArcadeDB vs. Drizzle vs. Microsoft Azure Cosmos DB vs. Teradata Aster

System Properties Comparison ArcadeDB vs. Drizzle vs. Microsoft Azure Cosmos DB vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

Globally distributed, horizontally scalable, multi-model database service

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.09
Rank	#355	Overall
	#48	Document stores
	#37	Graph DBMS
	#52	Key-value stores
	#34	Time Series DBMS

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

Website

arcadedb.com

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.arcadedb.com

learn.microsoft.com/azure/cosmos-db

Developer

Arcade Data

Drizzle project, originally started by Brian Aker

Microsoft

Teradata

Initial release

2021

2008

2014

2005

Current release

September 2021

7.2.4, September 2012

License

Commercial or Open Source

Open Source

Apache Version 2.0

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++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X

hosted

Linux

Data scheme

schema-free

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

with proprietary extensions

SQL-like query language

yes

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

JDBC

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

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Java

C
C++
Java
PHP

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

JavaScript

R packages

Triggers

hooks for callbacks inside the server can be used.

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

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.

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.