DBMS > Derby vs. MySQL vs. Splunk vs. Trafodion vs. Yanza

System Properties Comparison Derby vs. MySQL vs. Splunk vs. Trafodion vs. Yanza

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Widely used open source RDBMS

Analytics Platform for Big Data

Transactional SQL-on-Hadoop DBMS

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key/Value like access via memcached API

Search engine

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

yanza.com

Technical documentation

db.apache.org/derby/manuals/index.html

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

Apache Software Foundation, originally developed by HP

Yanza

Initial release

1997

1995

2003

2014

2015

Current release

10.17.1.0, November 2023

8.4.0, April 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache version 2

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

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

C and C++

C++, Java

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux

Windows

Data scheme

yes

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

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

ADO.NET
JDBC
ODBC

HTTP API

Supported programming languages

Java

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

All languages supporting JDBC/ODBC/ADO.Net

any language that supports HTTP calls

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

yes

Java Stored Procedures

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

yes, via HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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

yes

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

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

fine grained access rights according to SQL-standard

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.