DBMS > GeoMesa vs. HBase vs. NSDb vs. RDF4J vs. Sadas Engine

System Properties Comparison GeoMesa vs. HBase vs. NSDb vs. RDF4J vs. Sadas Engine

Editorial information provided by DB-Engines

Name

Description

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Website

Technical documentation

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

hbase.apache.org/book.html

nsdb.io/Architecture

rdf4j.org/documentation

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

Developer

CCRi and others

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

SADAS s.r.l.

Initial release

2014

2008

2017

2004

2006

Current release

4.0.5, February 2024

2.3.4, January 2021

8.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2

Open Source

Apache Version 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Scala

Java

Java, Scala

Java

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Linux
macOS

Linux
OS X
Unix
Windows

AIX
Linux
Windows

Data scheme

yes

schema-free, schema definition possible

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

yes: int, bigint, decimal, string

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.

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP API
Thrift

gRPC
HTTP REST
WebSocket

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC
Proprietary protocol

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

Java
Scala

Java
PHP
Python

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

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency or Eventual Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

in-memory storage is supported as well

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

managed by 'Learn by Usage'

User concepts

Access control

yes

depending on the DBMS used for storage

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

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

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

Best Practices from Rackspace for Modernizing a Legacy HBase/Solr Architecture Using AWS Services | Amazon Web ...
9 October 2023, AWS Blog

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

Cloudera Search Adds Search Engine Ease to Data on HDFS and Apache HBase
10 December 2023, Channel Futures

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

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

provided by Google News

L'azienda italiana Advanced System colpita dal ransomware. Lo avverte l'azienda con un comunicato stampa
29 December 2022, Red Hot Cyber

provided by Google News

Share this page