DBMS > 4D vs. GeoMesa vs. HBase vs. Riak TS

System Properties Comparison 4D vs. GeoMesa vs. HBase vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

www.4d.com

www.geomesa.org

hbase.apache.org

Technical documentation

developer.4d.com

www.geomesa.org/documentation/stable/user/index.html

hbase.apache.org/book.html

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

Developer

4D, Inc

CCRi and others

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Open Source, formerly Basho Technologies

Initial release

1984

2014

2008

2015

Current release

v20, April 2023

5.0.0, May 2024

2.3.4, January 2021

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache version 2

Open Source

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

Scala

Java

Erlang

Server operating systems

OS X
Windows

Linux
Unix
Windows

using Cygwin

Linux
OS X

Data scheme

yes

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

close to SQL 92

yes, limited

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

Java API
RESTful HTTP API
Thrift

HTTP API
Native Erlang Interface

Supported programming languages

4D proprietary IDE
PHP

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

yes

Coprocessors in Java

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

Multi-source replication
Source-replica replication

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

depending on storage layer

Immediate Consistency or Eventual Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

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.

depending on storage layer

yes

User concepts

Access control

Users and groups

yes

depending on the DBMS used for storage

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

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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

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.com

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

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page