DBMS > Adabas vs. DataFS vs. Geode vs. Snowflake vs. TigerGraph

System Properties Comparison Adabas vs. DataFS vs. Geode vs. Snowflake vs. TigerGraph

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

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Cloud-based data warehousing service for structured and semi-structured data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Graph DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

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

Technical documentation

dev.mobiland.com/Overview.xsp

geode.apache.org/docs

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Software AG

Mobiland AG

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Snowflake Computing Inc.

Initial release

1971

2018

2002

2014

2017

Current release

1.1.263, October 2022

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Windows

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux

Data scheme

yes

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language (OQL)

yes

SQL-like query language (GSQL)

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

.NET Client API
Proprietary client DLL
WinRT client

Java Client API
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Natural

.Net
C
C#
C++
VB.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

in Natural

user defined functions

yes

Triggers

no, except callback-events from server when changes happened

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

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

Proprietary Sharding system

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

yes, on a single node

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

User concepts

Access control

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

Windows-Profile

Access rights per client and object definable

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.