DBMS > EventStoreDB vs. Google Cloud Spanner vs. Graphite vs. MySQL

System Properties Comparison EventStoreDB vs. Google Cloud Spanner vs. Graphite vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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.

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	2.69
Rank	#101	Overall
	#51	Relational DBMS

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.eventstore.com

cloud.google.com/spanner

github.com/graphite-project/graphite-web

www.mysql.com

Technical documentation

developers.eventstore.com

cloud.google.com/spanner/docs

graphite.readthedocs.io

dev.mysql.com/doc

Developer

Event Store Limited

Google

Chris Davis

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2017

2006

1995

Current release

21.2, February 2021

9.0.0, July 2024

License

Commercial or Open Source

Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Python

C and C++

Server operating systems

Linux
Windows

hosted

Linux
Unix

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Query statements complying to ANSI 2011

yes

with proprietary extensions

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

HTTP API
Sockets

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

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

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

Multi-source replication with 3 replicas for regional instances.

none

Multi-source replication
Source-replica replication

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

none

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

locking

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.