DBMS > Google Cloud Spanner vs. KeyDB vs. MySQL vs. XTDB

System Properties Comparison Google Cloud Spanner vs. KeyDB vs. MySQL vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Widely used open source RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	2.69
Rank	#101	Overall
	#51	Relational DBMS

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

cloud.google.com/spanner

github.com/Snapchat/KeyDB
keydb.dev

www.mysql.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

cloud.google.com/spanner/docs

docs.keydb.dev

dev.mysql.com/doc

www.xtdb.com/docs

Developer

Google

EQ Alpha Technology Ltd.

Oracle

since 2010, originally MySQL AB, then Sun

Juxt Ltd.

Initial release

2017

2019

1995

2019

Current release

9.0.0, July 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

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

C++

C and C++

Clojure

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

yes, extensible-data-notation format

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Clojure
Java

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Strict serializable isolation

Optimistic locking, atomic execution of commands blocks and scripts

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 based on Google Cloud Identity and Access Management (IAM)

simple password-based access control and ACL

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.