DBMS > Adabas vs. FoundationDB vs. Hive vs. Microsoft Azure Data Explorer vs. Snowflake

System Properties Comparison Adabas vs. FoundationDB vs. Hive vs. Microsoft Azure Data Explorer vs. Snowflake

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

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

used typically together with the Natural programming platform

Ordered key-value store. Core features are complimented by layers.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Fully managed big data interactive analytics platform

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

Primary database model

Multivalue DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

column oriented

Relational DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	59.76
Rank	#18	Overall
	#12	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

github.com/apple/foundationdb

hive.apache.org

azure.microsoft.com/services/data-explorer

www.snowflake.com

Technical documentation

apple.github.io/foundationdb

cwiki.apache.org/confluence/display/Hive/Home

docs.microsoft.com/en-us/azure/data-explorer

docs.snowflake.net/manuals/index.html

Developer

Software AG

FoundationDB

Apache Software Foundation

initially developed by Facebook

Microsoft

Snowflake Computing Inc.

Initial release

1971

2013

2012

2019

2014

Current release

6.2.28, November 2020

3.1.3, April 2022

cloud service with continuous releases

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2

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

C++

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Windows

All OS with a Java VM

hosted

Data scheme

yes

schema-free

some layers support schemas

yes

Fixed schema with schema-less datatypes (dynamic)

yes

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

Typing

predefined data types such as float or date

yes

some layers support typing

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

supported in specific SQL layer only

SQL-like DML and DDL statements

Kusto Query Language (KQL), SQL subset

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

JDBC
ODBC
Thrift

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Natural

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C++
Java
PHP
Python

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

in SQL-layer only

yes

user defined functions and integration of map-reduce

Yes, possible languages: KQL, Python, R

user defined functions

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

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

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

selectable replication factor

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

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.

User concepts

Access control

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

Access rights for users, groups and roles

Azure Active Directory Authentication

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

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.