DBMS > Adabas vs. Google BigQuery vs. Microsoft Access vs. TinkerGraph vs. Yaacomo

System Properties Comparison Adabas vs. Google BigQuery vs. Microsoft Access vs. TinkerGraph 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

Large scale data warehouse service with append-only tables

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

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

Primary database model

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

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

cloud.google.com/bigquery

www.microsoft.com/en-us/microsoft-365/access

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

yaacomo.com

Technical documentation

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

Developer

Software AG

Google

Microsoft

Q2WEB GmbH

Initial release

1971

2010

1992

2009

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache 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

C++

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Windows

Not a real database server, but making use of DLLs

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

yes

but not compliant to any SQL standard

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/JSON API

ADO.NET
DAO
ODBC
OLE DB

TinkerPop 3

JDBC
ODBC

Supported programming languages

Natural

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Groovy
Java

Server-side scripts

Stored procedures

in Natural

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships 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

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

optional

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)

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

Google Cloud Identity & Access Management (IAM)

a simple user-level security was built in till version Access 2003

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.