DBMS > Adabas vs. Citus vs. Firebase Realtime Database vs. Google BigQuery

System Properties Comparison Adabas vs. Citus vs. Firebase Realtime Database vs. Google BigQuery

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

used typically together with the Natural programming platform

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Large scale data warehouse service with append-only tables

Primary database model

Secondary database models

Document store

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

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

www.citusdata.com

firebase.google.com/products/realtime-database

cloud.google.com/bigquery

Technical documentation

docs.citusdata.com

firebase.google.com/docs/database

cloud.google.com/bigquery/docs

Developer

Software AG

Google

acquired by Google 2014

Google

Initial release

1971

2010

2012

2010

Current release

8.1, December 2018

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

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

Linux

hosted

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

standard, with numerous extensions

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

Natural

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Java
JavaScript
Objective-C

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

limited functionality with using 'rules'

user defined functions

in JavaScript

Triggers

yes

Callbacks are triggered when data changes

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Source-replica replication

other methods possible by using 3rd party extensions

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Since BigQuery is designed for querying data

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)

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

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

Google Cloud Identity & Access Management (IAM)

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.