DBMS > Apache Impala vs. Apache Kylin vs. Snowflake vs. Solr vs. Tkrzw

System Properties Comparison Apache Impala vs. Apache Kylin vs. Snowflake vs. Solr vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

Cloud-based data warehousing service for structured and semi-structured data

A widely used distributed, scalable search engine based on Apache Lucene

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

Primary database model

Relational DBMS

Search engine

Key-value store

Secondary database models

Document store

Spatial DBMS

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	1.20
Rank	#175	Overall
	#80	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Score	0.09
Rank	#354	Overall
	#51	Key-value stores

Website

Technical documentation

impala.apache.org/impala-docs.html

kylin.apache.org/docs

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation, originally contributed from eBay Inc

Snowflake Computing Inc.

Apache Software Foundation

Mikio Hirabayashi

Initial release

2013

2015

2014

2006

2020

Current release

4.1.0, June 2022

3.1.0, July 2020

9.5.0, February 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

C++

Server operating systems

Linux

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
macOS

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

ANSI SQL for queries (using Apache Calcite)

yes

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

Java plugins

Triggers

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

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.