DBMS > Apache Phoenix vs. Oracle vs. PostGIS vs. RavenDB

System Properties Comparison Apache Phoenix vs. Oracle vs. PostGIS vs. RavenDB

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

Widely used RDBMS

Spatial extension of PostgreSQL

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Spatial DBMS

Document store

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

Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

phoenix.apache.org

www.oracle.com/database

postgis.net

ravendb.net

Technical documentation

phoenix.apache.org

docs.oracle.com/en/database

postgis.net/documentation

ravendb.net/docs

Developer

Apache Software Foundation

Oracle

Hibernating Rhinos

Initial release

2014

1980

2005

2010

Current release

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

23c, September 2023

3.4.2, February 2024

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted free version is available

Open Source

GPL v2.0

Open Source

AGPL version 3, commercial license available

Cloud-based only

Only available as a cloud service

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

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

Linux
macOS
Raspberry Pi
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

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (RQL)

APIs and other access methods

JDBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful 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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

PL/SQL

also stored procedures in Java possible

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

isolation level can be parameterized

ACID

ACID, Cluster-wide transaction available

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

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

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

Authorization levels configured per client per database

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.