DBMS > Apache Impala vs. KairosDB vs. MySQL vs. SiriDB vs. Sphinx

System Properties Comparison Apache Impala vs. KairosDB vs. MySQL vs. SiriDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Distributed Time Series DBMS based on Cassandra or H2

Widely used open source RDBMS

Open Source Time Series DBMS

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Search engine

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

impala.apache.org

github.com/kairosdb/kairosdb

www.mysql.com

siridb.com

sphinxsearch.com

Technical documentation

impala.apache.org/impala-docs.html

kairosdb.github.io

dev.mysql.com/doc

docs.siridb.com

sphinxsearch.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Oracle

since 2010, originally MySQL AB, then Sun

Cesbit

Sphinx Technologies Inc.

Initial release

2013

1995

2017

2001

Current release

4.1.0, June 2022

1.2.2, November 2018

8.3.0, January 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

Open Source

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

Java

C and C++

C++

Server operating systems

Linux

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

full-text index on all search fields

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript

Node.js
PHP
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++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate 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

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

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

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

simple rights management via user accounts

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.