DBMS > Apache Drill vs. MySQL vs. OrigoDB vs. Splunk

System Properties Comparison Apache Drill vs. MySQL vs. OrigoDB vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Widely used open source RDBMS

A fully ACID in-memory object graph database

Analytics Platform for Big Data

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

Technical documentation

drill.apache.org/docs

dev.mysql.com/doc

origodb.com/docs

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Splunk Inc.

Initial release

2012

1995

2009

under the name LiveDB

2003

Current release

1.20.3, January 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

HTTP REST

Supported programming languages

C++

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

.Net

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

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

Depending on the underlying data source

yes

Write ahead log

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

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.