DBMS > Graph Engine vs. MySQL vs. Splunk vs. YDB

System Properties Comparison Graph Engine vs. MySQL vs. Splunk vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Widely used open source RDBMS

Analytics Platform for Big Data

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Search engine

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	0.39
Rank	#269	Overall
	#43	Document stores
	#126	Relational DBMS

Website

www.graphengine.io

www.mysql.com

www.splunk.com

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

www.graphengine.io/docs/manual

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

ydb.tech/en/docs

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

Yandex

Initial release

2010

1995

2003

2019

Current release

9.0.0, July 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Limited free edition and free developer edition available

Open Source

Apache 2.0; commercial license 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

.NET and C

C and C++

Server operating systems

.NET

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

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

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

Splunk Search Processing Language for search commands

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

C#
C++
F#
Visual Basic

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

C#
Java
JavaScript
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

ACID

not for MyISAM storage engine

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Access rights for users and roles

Access rights defined for Yandex Cloud users

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.