DBMS > EXASOL vs. Graph Engine vs. Memcached vs. Microsoft SQL Server vs. Rockset

System Properties Comparison EXASOL vs. Graph Engine vs. Memcached vs. Microsoft SQL Server vs. Rockset

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS
Search engine

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	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

Website

www.exasol.com

www.graphengine.io

www.memcached.org

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

rockset.com

Technical documentation

www.exasol.com/resources

www.graphengine.io/docs/manual

github.com/memcached/memcached/wiki

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

docs.rockset.com

Developer

Exasol

Microsoft

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Rockset

Initial release

2000

2010

2003

1989

2019

Current release

1.6.25, March 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

BSD license

commercial

restricted free version is available

commercial

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

.NET and C

C++

Server operating systems

.NET

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

hosted

Data scheme

yes

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

Read-only SQL queries, including JOINs

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

RESTful HTTP API

Proprietary protocol

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

HTTP REST

Supported programming languages

Java
Lua
Python
R

C#
C++
F#
Visual Basic

.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

Server-side scripts

Stored procedures

user defined functions

yes

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

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

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

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 for users, groups and roles according to SQL-standard

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.