DBMS > Adabas vs. Couchbase vs. Google Cloud Datastore vs. NuoDB vs. Valentina Server

System Properties Comparison Adabas vs. Couchbase vs. Google Cloud Datastore vs. NuoDB vs. Valentina Server

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 distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Object-relational database and reports server

Primary database model

Multivalue DBMS

Document store

Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

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

www.couchbase.com

cloud.google.com/datastore

www.3ds.com/nuodb-distributed-sql-database

www.valentina-db.net

Technical documentation

docs.couchbase.com

cloud.google.com/datastore/docs

doc.nuodb.com

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Software AG

Couchbase, Inc.

Google

Dassault Systèmes

originally NuoDB, Inc.

Paradigma Software

Initial release

1971

2011

2008

2013

1999

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

5.7.5

License

Commercial or Open Source

commercial

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

limited edition free

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, C++, Go and Erlang

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL-like query language (GQL)

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

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ODBC

Supported programming languages

Natural

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

in Natural

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

using Google App Engine

Java, SQL

yes

Triggers

yes

via the TAP protocol

Callbacks using the Google Apps 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

Automatic Sharding

Sharding

data is dynamically stored/cached on the nodes where it is read/written

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication using Paxos

yes

Managed transparently by NuoDB

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

Ephemeral buckets

yes

Temporary table

yes

User concepts

Access control

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

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Standard SQL roles/ privileges, Administrative Users

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.