DBMS > Adabas vs. Amazon Neptune vs. Dgraph vs. Google BigQuery vs. Graph Engine

System Properties Comparison Adabas vs. Amazon Neptune vs. Dgraph vs. Google BigQuery vs. Graph Engine

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

Fast, reliable graph database built for the cloud

Distributed and scalable native Graph DBMS

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Primary database model

Graph DBMS
Key-value store

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Website

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

aws.amazon.com/neptune

dgraph.io

cloud.google.com/bigquery

www.graphengine.io

Technical documentation

aws.amazon.com/neptune/developer-resources

dgraph.io/docs

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

Developer

Software AG

Amazon

Dgraph Labs, Inc.

Google

Microsoft

Initial release

1971

2017

2016

2010

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

MIT License

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

.NET and C

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Linux
OS X
Windows

hosted

.NET

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

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

Natural

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

in Natural

user defined functions

in JavaScript

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

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

none

yes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Synchronous replication via Raft

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 and roles can be defined via the AWS Identity and Access Management (IAM)

Planned for future releases

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.