DBMS > AlaSQL vs. Apache Impala vs. MySQL vs. Splunk

System Properties Comparison AlaSQL vs. Apache Impala vs. MySQL vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Analytic DBMS for Hadoop

Widely used open source RDBMS

Analytics Platform for Big Data

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Website

Technical documentation

github.com/AlaSQL/alasql

impala.apache.org/impala-docs.html

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

Initial release

2014

2013

1995

2003

Current release

4.1.0, June 2022

9.0.0, July 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Implementation language

JavaScript

C++

C and C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like DML and DDL statements

yes

with proprietary extensions

Splunk Search Processing Language for search commands

APIs and other access methods

JavaScript API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

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

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

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

yes

only for local storage and DOM-storage

ACID

not for MyISAM storage engine

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

by using IndexedDB, SQL.JS or proprietary FileStorage

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.