DBMS > Hazelcast vs. Memcached vs. Microsoft SQL Server vs. Rockset vs. Tkrzw

System Properties Comparison Hazelcast vs. Memcached vs. Microsoft SQL Server vs. Rockset vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

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

Microsofts flagship relational DBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS
Spatial DBMS

Relational DBMS
Search engine

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

hazelcast.com

www.memcached.org

www.microsoft.com/en-us/sql-server

rockset.com

dbmx.net/tkrzw

Technical documentation

hazelcast.org/imdg/docs

github.com/memcached/memcached/wiki

learn.microsoft.com/en-US/sql/sql-server

docs.rockset.com

Developer

Hazelcast

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Rockset

Mikio Hirabayashi

Initial release

2008

2003

1989

2019

2020

Current release

5.3.6, November 2023

1.6.25, March 2024

SQL Server 2022, November 2022

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD license

commercial

restricted free version is available

commercial

Open Source

Apache Version 2.0

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
Unix
Windows

Linux
Windows

hosted

Linux
macOS

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

yes

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

yes

Read-only SQL queries, including JOINs

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Proprietary protocol

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Go
Java
JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

none

Repcached, a Memcached patch, provides this functionallity

yes, but depending on the SQL-Server Edition

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

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

using specific database classes

User concepts

Access control

Role-based access control

yes

using SASL (Simple Authentication and Security Layer) protocol

fine grained access rights according to SQL-standard

Access rights for users and organizations can be defined via Rockset console

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.