DBMS > ArcadeDB vs. Memcached vs. Microsoft Azure Cosmos DB vs. WakandaDB

System Properties Comparison ArcadeDB vs. Memcached vs. Microsoft Azure Cosmos DB vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

In-memory key-value store, originally intended for caching

Globally distributed, horizontally scalable, multi-model database service

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Object oriented DBMS

Secondary database models

Spatial DBMS

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

Score	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

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

Score	0.10
Rank	#356	Overall
	#17	Object oriented DBMS

Website

arcadedb.com

www.memcached.org

azure.microsoft.com/services/cosmos-db

wakanda.github.io

Technical documentation

docs.arcadedb.com

github.com/memcached/memcached/wiki

learn.microsoft.com/azure/cosmos-db

wakanda.github.io/doc

Developer

Arcade Data

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Wakanda SAS

Initial release

2021

2003

2014

2012

Current release

September 2021

1.6.27, May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD license

commercial

Open Source

AGPLv3, extended commercial license available

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

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language, no joins

SQL-like query language

APIs and other access methods

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

Proprietary protocol

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

RESTful HTTP API

Supported programming languages

Java

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

JavaScript

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

yes

Implicit feature of the cloud service

none

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights can be defined down to the item level

yes

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.