DBMS > EventStoreDB vs. MySQL vs. Snowflake vs. Solr vs. YTsaurus

System Properties Comparison EventStoreDB vs. MySQL vs. Snowflake vs. Solr vs. YTsaurus

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

Cloud-based data warehousing service for structured and semi-structured data

A widely used distributed, scalable search engine based on Apache Lucene

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Event Store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Search engine

Document store
Key-value store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.21
Rank	#324	Overall
	#45	Document stores
	#48	Key-value stores

Website

Technical documentation

developers.eventstore.com

dev.mysql.com/doc

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

ytsaurus.tech/docs/en

Developer

Event Store Limited

Oracle

since 2010, originally MySQL AB, then Sun

Snowflake Computing Inc.

Apache Software Foundation

Yandex

Initial release

2012

1995

2014

2006

2023

Current release

21.2, February 2021

8.4.0, April 2024

9.6.1, May 2024

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache Version 2

Open Source

Apache License, Version 2.0

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

C and C++

Java

C++

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Ubuntu

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

yes

Solr Parallel SQL Interface

YQL, an SQL-based language, is supported

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

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

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Java plugins

Triggers

yes

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

optimistic locking

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

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

Access Control Lists

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.