DBMS > MySQL vs. Oracle NoSQL vs. Splunk

System Properties Comparison MySQL vs. Oracle NoSQL vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Analytics Platform for Big Data

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.mysql.com

www.oracle.com/database/nosql/technologies/nosql

www.splunk.com

Technical documentation

dev.mysql.com/doc

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.splunk.com/Documentation/Splunk

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Splunk Inc.

Initial release

1995

2011

2003

Current release

8.3.0, January 2024

23.3, December 2023

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Limited free edition and free developer edition 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.

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

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Solaris SPARC/x86

Linux
OS X
Solaris
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL-like DML and DDL statements

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

HTTP REST

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

C
C#
Go
Java
JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual 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

configurable

ACID within a storage node (=shard)

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

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

off heap cache

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and 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.