DBMS > Datomic vs. Memcached vs. MySQL vs. PlanetScale

System Properties Comparison Datomic vs. Memcached vs. MySQL vs. PlanetScale

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Widely used open source RDBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

Technical documentation

docs.datomic.com

github.com/memcached/memcached/wiki

dev.mysql.com/doc

planetscale.com/docs

Developer

Cognitect

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

PlanetScale

Initial release

2012

2003

1995

2020

Current release

1.0.7075, December 2023

1.6.27, May 2024

8.4.0, April 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java, Clojure

C and C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

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

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Clojure
Java

.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

yes

Transaction Functions

yes

proprietary syntax

yes

proprietary syntax

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

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.