DBMS > Adabas vs. Datomic vs. FatDB vs. GeoMesa vs. Yaacomo

System Properties Comparison Adabas vs. Datomic vs. FatDB vs. GeoMesa 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

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

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Primary database model

Multivalue DBMS

Relational DBMS

Document store
Key-value store

Spatial 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	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Website

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

www.datomic.com

www.geomesa.org

yaacomo.com

Technical documentation

docs.datomic.com

www.geomesa.org/documentation/stable/user/index.html

Developer

Software AG

Cognitect

FatCloud

CCRi and others

Q2WEB GmbH

Initial release

1971

2012

2014

2009

Current release

1.0.6735, June 2023

4.0.5, February 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache License 2.0

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

Java, Clojure

Scala

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

All OS with a Java VM

Windows

Android
Linux
Windows

Data scheme

yes

schema-free

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

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

RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

Natural

Clojure
Java

Server-side scripts

Stored procedures

in Natural

yes

Transaction Functions

yes

via applications

Triggers

By using transaction functions

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

But extensive use of caching in the application peers

Sharding

depending on storage layer

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

none

But extensive use of caching in the application peers

selectable replication factor

depending on storage layer

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

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

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

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

depending on storage layer

yes

User concepts

Access control

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

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

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

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

IBM buys 50-year-old Software AG's enterprise tech units for €2.13B in cash
18 December 2023, The Register

A Second Look at LzLabs' Mainframe Migration
28 June 2017, Virtualization Review

provided by Google News

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Zoona Case Study
16 December 2017, AWS Blog

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Relational, NoSQL, Ledger Databases work, not Permissioned Blockchains.
13 January 2019, hackernoon.com

provided by Google News

Share this page