DBMS > Apache Impala vs. Splunk vs. Tkrzw vs. Vitess vs. Yaacomo

System Properties Comparison Apache Impala vs. Splunk vs. Tkrzw vs. Vitess vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Analytic DBMS for Hadoop

Analytics Platform for Big Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Scalable, distributed, cloud-native DBMS, extending MySQL

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

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	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

yaacomo.com

Technical documentation

impala.apache.org/impala-docs.html

docs.splunk.com/Documentation/Splunk

vitess.io/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Splunk Inc.

Mikio Hirabayashi

The Linux Foundation, PlanetScale

Q2WEB GmbH

Initial release

2013

2003

2020

2013

2009

Current release

4.1.0, June 2022

0.9.3, August 2020

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0, commercial licenses available

commercial

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

C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

Linux
macOS

Docker
Linux
macOS

Android
Linux
Windows

Data scheme

yes

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-like DML and DDL statements

Splunk Search Processing Language for search commands

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

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

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

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

none

Multi-source replication
Source-replica replication

Source-replica 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

Eventual Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID at shard level

ACID

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

In-memory capabilities

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

yes

using specific database classes

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

Apache Impala 4 Supports Operator Multi-Threading
29 July 2021, iProgrammer

Apache Impala becomes Top-Level Project
28 November 2017, SDTimes.com

StarRocks Brings Speedy OLAP Database to the Cloud
14 July 2022, Datanami

Apache Doris just 'graduated': Why care about this SQL data warehouse
24 June 2022, InfoWorld

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

Share this page