DBMS > Apache Impala vs. Apache Phoenix vs. Snowflake vs. Vertica

System Properties Comparison Apache Impala vs. Apache Phoenix vs. Snowflake vs. Vertica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Relational DBMS

Column oriented

Secondary database models

Document store

Spatial DBMS
Time Series DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	10.68
Rank	#43	Overall
	#27	Relational DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

phoenix.apache.org

docs.snowflake.net/manuals/index.html

vertica.com/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

Snowflake Computing Inc.

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2013

2014

2005

Current release

4.1.0, June 2022

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

12.0.3, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

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

Linux
Unix
Windows

hosted

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

yes

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

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

SQL-like DML and DDL statements

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

JDBC
ODBC

JDBC

CLI Client
JDBC
ODBC

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

JavaScript (Node.js)
Python

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

similar concept for controling cloud resources

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

yes

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Hadoop integration

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or 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

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.