DBMS > Adabas vs. Axibase vs. Datomic vs. Google Cloud Datastore vs. SAP HANA

System Properties Comparison Adabas vs. Axibase vs. Datomic vs. Google Cloud Datastore vs. SAP HANA

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	0.32
Rank	#288	Overall
	#25	Time Series DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

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

axibase.com/docs/atsd/finance

www.datomic.com

cloud.google.com/datastore

www.sap.com/products/hana.html

Technical documentation

docs.datomic.com

cloud.google.com/datastore/docs

help.sap.com/hana

Developer

Software AG

Axibase Corporation

Cognitect

Google

SAP

Initial release

1971

2013

2012

2008

2010

Current release

15585

1.0.6735, June 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

limited edition free

commercial

Cloud-based only

Only available as a cloud service

yes

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

Java, Clojure

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

All OS with a Java VM

hosted

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

yes, details here

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

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language

SQL-like query language (GQL)

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
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

Natural

Go
Java
PHP
Python
R
Ruby

Clojure
Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

yes

Transaction Functions

using Google App Engine

SQLScript, R

Triggers

yes

By using transaction functions

Callbacks using the Google Apps Engine

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

none

But extensive use of caching in the application peers

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Source-replica replication

none

But extensive use of caching in the application peers

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.