DBMS > Memcached vs. Microsoft Azure Cosmos DB vs. OpenEdge vs. VoltDB

System Properties Comparison Memcached vs. Microsoft Azure Cosmos DB vs. OpenEdge vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

Application development environment with integrated database management system

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

Key-value store

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	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	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.memcached.org

azure.microsoft.com/services/cosmos-db

www.progress.com/openedge

www.voltdb.com

Technical documentation

github.com/memcached/memcached/wiki

learn.microsoft.com/azure/cosmos-db

documentation.progress.com/output/ua/OpenEdge_latest

docs.voltdb.com

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Progress Software Corporation

VoltDB Inc.

Initial release

2003

2014

1984

2010

Current release

1.6.27, May 2024

OpenEdge 12.2, March 2020

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD license

commercial

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

Java, C++

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

for development

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

close to SQL 92

yes

only a subset of SQL 99

APIs and other access methods

Proprietary protocol

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

JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.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

Progress proprietary ABL (Advanced Business Language)

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

Java

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

Implicit feature of the cloud service

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

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

Snapshots and command logging

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

Users and groups

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.