DBMS > Geode vs. Memcached vs. Microsoft Azure Cosmos DB vs. SingleStore vs. XTDB

System Properties Comparison Geode vs. Memcached vs. Microsoft Azure Cosmos DB vs. SingleStore vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Globally distributed, horizontally scalable, multi-model database service

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

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

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

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

geode.apache.org

www.memcached.org

azure.microsoft.com/services/cosmos-db

www.singlestore.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

geode.apache.org/docs

github.com/memcached/memcached/wiki

learn.microsoft.com/azure/cosmos-db

docs.singlestore.com

www.xtdb.com/docs

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

SingleStore Inc.

Juxt Ltd.

Initial release

2002

2003

2014

2013

2019

Current release

1.1, February 2017

1.6.29, June 2024

8.5, January 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD license

commercial

free developer edition available

Open Source

MIT License

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

Clojure

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux

64 bit version required

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

yes, extensible-data-notation format

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

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

but no triggers and foreign keys

limited SQL, making use of Apache Calcite

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Proprietary protocol

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

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

HTTP REST
JDBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

.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

Bash
C
C#
Java
JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

Triggers

yes

Cache Event Listeners

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

yes

Implicit feature of the cloud service

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 per client and object definable

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights can be defined down to the item level

Fine grained access control via users, groups 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.