DBMS > EsgynDB vs. HBase vs. PostGIS vs. Riak KV

System Properties Comparison EsgynDB vs. HBase vs. PostGIS vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Wide-column store based on Apache Hadoop and on concepts of BigTable

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

Primary database model

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

Secondary database models

Relational DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

www.esgyn.cn

hbase.apache.org

postgis.net

Technical documentation

hbase.apache.org/book.html

postgis.net/documentation

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

Developer

Esgyn

Apache Software Foundation

Apache top-level project, originally developed by Powerset

OpenSource, formerly Basho Technologies

Initial release

2015

2008

2005

2009

Current release

2.3.4, January 2021

3.4.2, February 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

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

C++, Java

Java

Erlang

Server operating systems

Linux

Linux
Unix
Windows

using Cygwin

Linux
OS X

Data scheme

yes

schema-free, schema definition possible

yes

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Java API
RESTful HTTP API
Thrift

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Coprocessors in Java

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"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

yes

based on PostgreSQL

yes, using Riak Security

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)

Why is Hadoop not listed in the DB-Engines Ranking?
13 May 2013, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Less Components, Higher Performance: Apache Doris instead of ClickHouse, MySQL, Presto, and HBase
20 October 2023, hackernoon.com

What Is HBase?
19 August 2021, IBM

HBase: The database big data left behind
6 May 2016, InfoWorld

Monitor Apache HBase on Amazon EMR using Amazon Managed Service for Prometheus and Amazon Managed ...
13 February 2023, AWS Blog

HydraBase – The evolution of HBase@Facebook
5 June 2014, Facebook Engineering

provided by Google News

Share this page