DBMS > Apache Phoenix vs. SAP HANA vs. SAP SQL Anywhere vs. YottaDB

System Properties Comparison Apache Phoenix vs. SAP HANA vs. SAP SQL Anywhere vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

In-memory, column based data store. Available as appliance or cloud service

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

phoenix.apache.org

www.sap.com/products/hana.html

www.sap.com/products/technology-platform/sql-anywhere.html

yottadb.com

Technical documentation

phoenix.apache.org

help.sap.com/hana

help.sap.com/docs/SAP_SQL_Anywhere

yottadb.com/resources/documentation

Developer

Apache Software Foundation

SAP

formerly Sybase

YottaDB, LLC

Initial release

2014

2010

1992

2001

Current release

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

2.0 SPS07 (April 4, 2023), April 2023

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

Linux
Unix
Windows

Appliance or cloud-service

AIX
HP-UX
Linux
OS X
Solaris
Windows

Docker
Linux

Data scheme

yes

late-bound, schema-on-read capabilities

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

SQL

Support of SQL

yes

by using the Octo plugin

APIs and other access methods

JDBC

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

Database mirroring

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

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

optimistic locking

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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.