DBMS > Derby vs. GeoMesa vs. Riak TS vs. SAP HANA

System Properties Comparison Derby vs. GeoMesa vs. Riak TS vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

db.apache.org/derby

www.geomesa.org

www.sap.com/products/hana.html

Technical documentation

db.apache.org/derby/manuals/index.html

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

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

help.sap.com/hana

Developer

Apache Software Foundation

CCRi and others

Open Source, formerly Basho Technologies

SAP

Initial release

1997

2014

2015

2010

Current release

10.17.1.0, November 2023

5.0.0, May 2024

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache License 2.0

Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Scala

Erlang

Server operating systems

All OS with a Java VM

Linux
OS X

Appliance or cloud-service

Data scheme

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

yes, limited

yes

APIs and other access methods

JDBC

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

Java

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

Erlang

SQLScript, R

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

selectable replication factor

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets 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

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

yes

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.