DBMS > Hazelcast vs. Memcached vs. Microsoft Azure Cosmos DB vs. Realm

System Properties Comparison Hazelcast vs. Memcached vs. Microsoft Azure Cosmos DB vs. Realm

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

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

Globally distributed, horizontally scalable, multi-model database service

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

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	7.41
Rank	#52	Overall
	#8	Document stores

Website

hazelcast.com

www.memcached.org

azure.microsoft.com/services/cosmos-db

realm.io

Technical documentation

hazelcast.org/imdg/docs

github.com/memcached/memcached/wiki

learn.microsoft.com/azure/cosmos-db

realm.io/docs

Developer

Hazelcast

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Realm, acquired by MongoDB in May 2019

Initial release

2008

2003

2014

Current release

5.3.6, November 2023

1.6.27, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD license

commercial

Open Source

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

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Unix
Windows

hosted

Android
Backend: server-less
iOS
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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Proprietary protocol

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

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
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

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Events

JavaScript

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

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

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

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.

yes

In-Memory realm

User concepts

Access control

Role-based 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.