DBMS > Adabas vs. Apache Drill vs. ArcadeDB vs. Google BigQuery vs. Yaacomo

System Properties Comparison Adabas vs. Apache Drill vs. ArcadeDB vs. Google BigQuery vs. Yaacomo

Editorial information provided by DB-Engines

Name

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

Large scale data warehouse service with append-only tables

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

Primary database model

Multivalue DBMS

Document store
Relational DBMS

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.02
Rank	#366	Overall
	#50	Document stores
	#38	Graph DBMS
	#53	Key-value stores
	#36	Time Series DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

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

drill.apache.org

arcadedb.com

cloud.google.com/bigquery

yaacomo.com

Technical documentation

drill.apache.org/docs

docs.arcadedb.com

cloud.google.com/bigquery/docs

Developer

Software AG

Apache Software Foundation

Arcade Data

Google

Q2WEB GmbH

Initial release

1971

2012

2021

2010

2009

Current release

1.20.3, January 2023

September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2.0

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

Linux
OS X
Windows

All OS with a Java VM

hosted

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

SQL SELECT statement is SQL:2003 compliant

SQL-like query language, no joins

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
RESTful HTTP API

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

Natural

C++

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

user defined functions

in JavaScript

Triggers

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

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

Depending on the underlying data source

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.