DBMS > Apache Phoenix vs. CockroachDB vs. EDB Postgres vs. Oracle vs. Yanza

System Properties Comparison Apache Phoenix vs. CockroachDB vs. EDB Postgres vs. Oracle 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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

Widely used RDBMS

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

phoenix.apache.org

www.cockroachlabs.com

www.enterprisedb.com

www.oracle.com/database

yanza.com

Technical documentation

phoenix.apache.org

www.cockroachlabs.com/docs

www.enterprisedb.com/docs

docs.oracle.com/en/database

Developer

Apache Software Foundation

Cockroach Labs

EnterpriseDB

Oracle

Yanza

Initial release

2014

2015

2005

1980

2015

Current release

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

24.1.0, May 2024

14, December 2021

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0, commercial license available

commercial

BSD for PostgreSQL-components

commercial

restricted free version is available

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

Server operating systems

Linux
Unix
Windows

Linux
macOS
Windows

Linux
Windows

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

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

dynamic schema

yes

Schemaless in JSON and XML columns

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

yes, wire compatible with PostgreSQL

yes

standard with numerous extensions

yes

with proprietary extensions

APIs and other access methods

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

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

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

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

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

horizontal partitioning

by hash, list or range

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using RAFT

Multi-source replication

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

yes, multi-version concurrency control (MVCC)

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

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

User concepts

Access control

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

Role-based access control

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.