DBMS > Amazon Redshift vs. Apache Phoenix vs. Solr vs. Sphinx vs. Yanza

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Solr vs. Sphinx vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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

A widely used distributed, scalable search engine based on Apache Lucene

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

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Search engine

Time Series DBMS

Secondary database models

Spatial 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	42.91
Rank	#24	Overall
	#3	Search engines

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

phoenix.apache.org

solr.apache.org

sphinxsearch.com

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

solr.apache.org/resources.html

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Sphinx Technologies Inc.

Yanza

Initial release

2012

2014

2006

2001

2015

Current release

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

9.6.0, April 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2

Open Source

GPL version 2, commercial licence available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

restricted

yes

All search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Solr Parallel SQL Interface

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

JDBC

Java API
RESTful HTTP/JSON API

Proprietary protocol

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Java plugins

Triggers

yes

User configurable commands triggered on index changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

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

optimistic locking

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

yes

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.