DBMS > Adabas vs. Amazon Redshift vs. GeoMesa vs. Splice Machine vs. STSdb

System Properties Comparison Adabas vs. Amazon Redshift vs. GeoMesa vs. Splice Machine vs. STSdb

Editorial information provided by DB-Engines

Name

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Large scale data warehouse service for use with business intelligence tools

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

aws.amazon.com/redshift

www.geomesa.org

splicemachine.com

github.com/STSSoft/STSdb4

Technical documentation

docs.aws.amazon.com/redshift

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

splicemachine.com/how-it-works

Developer

Software AG

Amazon (based on PostgreSQL)

CCRi and others

Splice Machine

STS Soft SC

Initial release

1971

2012

2014

2011

Current release

5.0.0, May 2024

3.1, March 2021

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

AGPL 3.0, commercial license available

Open Source

GPLv2, commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Linux
OS X
Solaris
Windows

Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

restricted

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

does not fully support an SQL-standard

yes

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

.NET Client API

Supported programming languages

Natural

All languages supporting JDBC/ODBC

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C#
Java

Server-side scripts

Stored procedures

in Natural

user defined functions

in Python

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

Sharding

depending on storage layer

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

depending on storage layer

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.