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

System Properties Comparison Apache Impala vs. Apache Kylin vs. PouchDB vs. Snowflake 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

JavaScript DBMS with an API inspired by CouchDB

Cloud-based data warehousing service for structured and semi-structured 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

Primary database model

Secondary database models

Document store

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	2.35
Rank	#116	Overall
	#22	Document stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

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

Website

Technical documentation

impala.apache.org/impala-docs.html

kylin.apache.org/docs

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation, originally contributed from eBay Inc

Apache Software Foundation

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2013

2015

2012

2014

2020

Current release

4.1.0, June 2022

3.1.0, July 2020

7.1.1, June 2019

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

commercial

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

JavaScript

C++

Server operating systems

Linux

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

hosted

Linux
macOS

Data scheme

yes

schema-free

yes

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

schema-free

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 views

SQL

Support of SQL

SQL-like DML and DDL statements

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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.