DBMS > Adabas vs. AgensGraph vs. Datomic vs. EsgynDB vs. Google BigQuery

System Properties Comparison Adabas vs. AgensGraph vs. Datomic vs. EsgynDB vs. Google BigQuery

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

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Large scale data warehouse service with append-only tables

Primary database model

Multivalue DBMS

Graph DBMS
Relational DBMS

Relational DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

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

bitnine.net/agensgraph

www.datomic.com

www.esgyn.cn

cloud.google.com/bigquery

Technical documentation

bitnine.net/documentation

docs.datomic.com

cloud.google.com/bigquery/docs

Developer

Software AG

Bitnine Global Inc.

Cognitect

Esgyn

Google

Initial release

1971

2016

2012

2015

2010

Current release

2.1, December 2018

1.0.6735, June 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

limited edition free

commercial

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, Clojure

C++, Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Windows

All OS with a Java VM

Linux

hosted

Data scheme

yes

depending on used data model

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

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

Cypher Query Language
JDBC

RESTful HTTP API

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

Supported programming languages

Natural

C
Java
JavaScript
Python

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

yes

Transaction Functions

Java Stored Procedures

user defined functions

in JavaScript

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

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

no, but can be realized using table inheritance

none

But extensive use of caching in the application peers

Sharding

none

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 between multi datacenters

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

User concepts

Access control

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

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.