DBMS > CrateDB vs. EXASOL vs. Memcached vs. MySQL

System Properties Comparison CrateDB vs. EXASOL vs. Memcached vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

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

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

Widely used open source RDBMS

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

cratedb.com/docs

www.exasol.com/resources

github.com/memcached/memcached/wiki

dev.mysql.com/doc

Developer

Crate

Exasol

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2000

2003

1995

Current release

5.8.1, August 2024

1.6.29, June 2024

9.0.0, July 2024

License

Commercial or Open Source

Open Source

commercial

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

Java
Lua
Python
R

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions (Javascript)

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Read-after-write consistency on record level

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

rights management via user accounts

Access rights for users, groups and roles according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or 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.