DBMS > Apache Impala vs. Apache Kylin vs. OrigoDB vs. Snowflake vs. Trafodion

System Properties Comparison Apache Impala vs. Apache Kylin vs. OrigoDB vs. Snowflake vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

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

A fully ACID in-memory object graph database

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

kylin.apache.org/docs

origodb.com/docs

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation, originally contributed from eBay Inc

Robert Friberg et al

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2013

2015

2009

under the name LiveDB

2014

Current release

4.1.0, June 2022

3.1.0, July 2020

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

commercial

Open Source

Apache 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++, Java

Server operating systems

Linux

Linux
Windows

hosted

Linux

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

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

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

user defined functions

Java Stored Procedures

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Role based authorization

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

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.