DBMS > Amazon Redshift vs. Apache Phoenix vs. Heroic vs. Sphinx vs. Warp 10

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Heroic vs. Sphinx vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Open source search engine for searching in data from different sources, e.g. relational databases

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

phoenix.apache.org

github.com/spotify/heroic

sphinxsearch.com

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

spotify.github.io/heroic

sphinxsearch.com/docs

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Spotify

Sphinx Technologies Inc.

SenX

Initial release

2012

2014

2001

2015

Current release

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

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

Open Source

Apache License 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

Java

C++

Java

Server operating systems

hosted

Linux
Unix
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

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.

Secondary indexes

restricted

yes

via Elasticsearch

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Proprietary protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

WarpScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

The original contents of fields are not stored in the Sphinx index.

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

fine grained access rights according to SQL-standard

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.