DBMS > Amazon Redshift vs. Apache Phoenix vs. Sphinx vs. STSdb vs. SWC-DB

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Sphinx vs. STSdb vs. SWC-DB

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

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Time Series DBMS

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	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

aws.amazon.com/redshift

phoenix.apache.org

sphinxsearch.com

github.com/STSSoft/STSdb4

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Sphinx Technologies Inc.

STS Soft SC

Alex Kashirin

Initial release

2012

2014

2001

2011

2020

Current release

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

3.5.1, February 2023

4.0.8, September 2015

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2, commercial licence available

Open Source

GPLv2, commercial license available

Open Source

GPL V3

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++

Server operating systems

hosted

Linux
Unix
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

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)

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC

Proprietary protocol

.NET Client API

Proprietary protocol
Thrift

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

C#
Java

C++

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

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

Immediate Consistency

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

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.