DBMS > Adabas vs. CouchDB vs. Geode vs. Google BigQuery

System Properties Comparison Adabas vs. CouchDB vs. Geode 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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Large scale data warehouse service with append-only tables

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

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

couchdb.apache.org

geode.apache.org

cloud.google.com/bigquery

Technical documentation

docs.couchdb.org/en/stable

geode.apache.org/docs

cloud.google.com/bigquery/docs

Developer

Software AG

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Initial release

1971

2005

2002

2010

Current release

3.3.3, December 2023

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Erlang

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

the JDK (8 or later) is also required

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.

Secondary indexes

yes

via views

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language (OQL)

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

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

Natural

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

View functions in JavaScript

user defined functions

in JavaScript

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

Sharding

improved architecture with release 2.0

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication
Source-replica replication

Multi-source replication

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

Foreign keys

Referential integrity

Transaction concepts

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

ACID

atomic operations within a single document possible

yes, on a single node

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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.

yes

User concepts

Access control

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

Access rights for users can be defined per database

Access rights per client and object definable

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.