DBMS > Adabas vs. FatDB vs. Graph Engine vs. OrigoDB vs. Yaacomo

System Properties Comparison Adabas vs. FatDB vs. Graph Engine vs. OrigoDB vs. Yaacomo

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

used typically together with the Natural programming platform

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A fully ACID in-memory object graph database

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Multivalue DBMS

Document store
Key-value store

Graph DBMS
Key-value store

Document store
Object oriented DBMS

Relational DBMS

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Website

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

www.graphengine.io

origodb.com

yaacomo.com

Technical documentation

www.graphengine.io/docs/manual

origodb.com/docs

Developer

Software AG

FatCloud

Microsoft

Robert Friberg et al

Q2WEB GmbH

Initial release

1971

2012

2010

2009

under the name LiveDB

2009

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Windows

.NET

Linux
Windows

Android
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

Via inetgration in SQL Server

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

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP API

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Supported programming languages

Natural

C#
C++
F#
Visual Basic

.Net

Server-side scripts

Stored procedures

in Natural

yes

via applications

yes

Triggers

yes

via applications

yes

Domain Events

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

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

selectable replication factor

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Write ahead log

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)

Can implement custom security layer via applications

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Modernize Natural and Adabas Workloads on AWS with Advanced's Application Transparency Platform | Amazon Web ...
1 April 2024, AWS Blog

Deploying Software AG Adabas and Natural Workloads on AWS | Amazon Web Services
25 May 2021, AWS Blog

State agency proves DevOps and mainframes can coexist
13 April 2024, SiliconANGLE News

COBOL Is Taking Heat, but These Other Legacy Languages Could Burn You
1 October 2020, DevOps.com

Don't rewrite legacy systems for hybrid cloud – integrate them
1 February 2022, ITWeb

provided by Google News

Trinity
2 June 2023, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

How Google and Microsoft taught search to "understand" the Web
6 June 2012, Ars Technica

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

provided by Google News

Share this page