DBMS > Adabas vs. FatDB vs. Snowflake vs. Sqrrl

System Properties Comparison Adabas vs. FatDB vs. Snowflake vs. Sqrrl

Please select another system to include it in the comparison.

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been 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.

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Multivalue DBMS

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.snowflake.com

sqrrl.com

Technical documentation

docs.snowflake.net/manuals/index.html

Developer

Software AG

FatCloud

Snowflake Computing Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

1971

2012

2014

2012

License

Commercial or Open Source

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Windows

hosted

Linux

Data scheme

yes

schema-free

yes

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

schema-free

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

CLI Client
JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

Natural

JavaScript (Node.js)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

in Natural

yes

via applications

user defined functions

Triggers

yes

via applications

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

Sharding

yes

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

selectable replication factor

yes

selectable replication factor

making use of Hadoop

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

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.

User concepts

Access control

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

Can implement custom security layer via applications

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.