DBMS > Adabas vs. Amazon DynamoDB vs. Coveo vs. GeoSpock vs. Postgres-XL

System Properties Comparison Adabas vs. Amazon DynamoDB vs. Coveo vs. GeoSpock vs. Postgres-XL

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

used typically together with the Natural programming platform

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Spatial and temporal data processing engine for extreme data scale

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Multivalue DBMS

Document store
Key-value store

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

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

aws.amazon.com/dynamodb

www.coveo.com

geospock.com

www.postgres-xl.org

Technical documentation

docs.aws.amazon.com/dynamodb

docs.coveo.com

www.postgres-xl.org/documentation

Developer

Software AG

Amazon

Coveo

GeoSpock

Initial release

1971

2012

2014

since 2012, originally named StormDB

Current release

2.0, September 2019

10 R1, October 2018

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Mozilla public license

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

Java, Javascript

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Linux
macOS

Data scheme

yes

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

XML type, but no XML query functionality

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

ANSI SQL for query only (using Presto)

yes

distributed, parallel query execution

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

RESTful HTTP API

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Natural

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

in Natural

user defined functions

Triggers

yes

by integration with AWS Lambda

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

yes

Automatic sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

yes

ACID

MVCC

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.

User concepts

Access control

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

granular access controls, API key management, content filters

Access rights for users can be defined per table

fine grained access rights 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.