DBMS > Apache Phoenix vs. Oracle vs. Sphinx vs. Tkrzw vs. Yanza

System Properties Comparison Apache Phoenix vs. Oracle vs. Sphinx vs. Tkrzw vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

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

Widely used RDBMS

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

phoenix.apache.org

www.oracle.com/database

sphinxsearch.com

dbmx.net/tkrzw

yanza.com

Technical documentation

phoenix.apache.org

docs.oracle.com/en/database

sphinxsearch.com/docs

Developer

Apache Software Foundation

Oracle

Sphinx Technologies Inc.

Mikio Hirabayashi

Yanza

Initial release

2014

1980

2001

2020

2015

Current release

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

23c, September 2023

3.5.1, February 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

Open Source

Apache Version 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

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

C++

Server operating systems

Linux
Unix
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
macOS

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Proprietary protocol

HTTP API

Supported programming languages

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

PL/SQL

also stored procedures in Java possible

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

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

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

using specific database classes

User concepts

Access control

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

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.