DBMS > Heroic vs. MySQL vs. Sphinx vs. Splice Machine

System Properties Comparison Heroic vs. MySQL vs. Sphinx vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used open source RDBMS

Open source search engine for searching in data from different sources, e.g. relational databases

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

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

github.com/spotify/heroic

www.mysql.com

sphinxsearch.com

splicemachine.com

Technical documentation

spotify.github.io/heroic

dev.mysql.com/doc

sphinxsearch.com/docs

splicemachine.com/how-it-works

Developer

Spotify

Oracle

since 2010, originally MySQL AB, then Sun

Sphinx Technologies Inc.

Splice Machine

Initial release

2014

1995

2001

2014

Current release

8.4.0, April 2024

3.5.1, February 2023

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL version 2, commercial licence 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++

C++

Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
NetBSD
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

via Elasticsearch

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (SphinxQL)

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

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

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Partitioning is done manually, search queries against distributed index is supported

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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, 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.