DBMS > Apache Phoenix vs. PostGIS vs. Riak KV vs. Sadas Engine

System Properties Comparison Apache Phoenix vs. PostGIS vs. Riak KV vs. Sadas Engine

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

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Relational DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

phoenix.apache.org

postgis.net

www.sadasengine.com

Technical documentation

phoenix.apache.org

postgis.net/documentation

www.tiot.jp/riak-docs/riak/kv/latest

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Apache Software Foundation

OpenSource, formerly Basho Technologies

SADAS s.r.l.

Initial release

2014

2005

2009

2006

Current release

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

3.4.2, February 2024

3.2.0, December 2022

8.0

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

free trial version 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

Erlang

C++

Server operating systems

Linux
Unix
Windows

Linux
OS X

AIX
Linux
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

HTTP API
Native Erlang Interface

JDBC
ODBC
Proprietary protocol

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

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

managed by 'Learn by Usage'

User concepts

Access control

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

yes

based on PostgreSQL

yes, using Riak Security

Access rights for users, groups and roles 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Supercharge SQL on Your Data in Apache HBase with Apache Phoenix | Amazon Web Services
2 June 2016, AWS Blog

Bridge the SQL-NoSQL gap with Apache Phoenix
4 February 2016, InfoWorld

Apache Calcite, FreeMarker, Gora, Phoenix, and Solr updated
27 March 2017, SDTimes.com

What Is HBase? (Definition, Uses, Benefits, Features)
22 December 2022, Built In

Azure HDInsight Analytics Platform Now Supports Apache Hadoop 3.0
18 April 2019, eWeek

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page