DBMS > Apache Drill vs. Apache Pinot vs. MySQL vs. Splice Machine

System Properties Comparison Apache Drill vs. Apache Pinot vs. MySQL vs. Splice Machine

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

Realtime distributed OLAP datastore, designed to answer OLAP queries with low latency

Widely used open source RDBMS

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

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	0.38
Rank	#275	Overall
	#126	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

Technical documentation

drill.apache.org/docs

docs.pinot.apache.org

dev.mysql.com/doc

splicemachine.com/how-it-works

Developer

Apache Software Foundation

Apache Software Foundation and contributors

Oracle

since 2010, originally MySQL AB, then Sun

Splice Machine

Initial release

2012

2015

1995

2014

Current release

1.20.3, January 2023

1.0.0, September 2023

8.4.0, April 2024

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL 3.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.

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

Java

Server operating systems

Linux
OS X
Windows

All OS with a Java JDK11 or higher

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

C++

Go
Java
Python

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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

Depending on the underlying data source

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

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