DBMS > Adabas vs. FatDB vs. Memcached vs. Snowflake vs. Yaacomo

System Properties Comparison Adabas vs. FatDB vs. Memcached vs. Snowflake 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.

In-memory key-value store, originally intended for caching

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

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

Primary database model

Multivalue DBMS

Document store
Key-value store

Key-value store

Relational DBMS

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	20.74
Rank	#32	Overall
	#4	Key-value stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.memcached.org

www.snowflake.com

yaacomo.com

Technical documentation

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Software AG

FatCloud

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Q2WEB GmbH

Initial release

1971

2012

2003

2014

2009

Current release

1.6.25, March 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Windows

FreeBSD
Linux
OS X
Unix
Windows

hosted

Android
Linux
Windows

Data scheme

yes

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

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

Proprietary protocol

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

Natural

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

yes

via applications

user defined functions

Triggers

yes

via applications

similar concept for controling cloud resources

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

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

selectable replication factor

none

Repcached, a Memcached patch, provides this functionallity

yes

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

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

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

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.