DBMS > Adabas vs. Google BigQuery vs. Manticore Search vs. Riak KV

System Properties Comparison Adabas vs. Google BigQuery vs. Manticore Search vs. Riak KV

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

Large scale data warehouse service with append-only tables

Multi-storage database for search, including full-text search.

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	2.64
Rank	#104	Overall
	#1	Multivalue DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Website

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

cloud.google.com/bigquery

manticoresearch.com

Technical documentation

cloud.google.com/bigquery/docs

manual.manticoresearch.com

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Software AG

Google

Manticore Software

OpenSource, formerly Basho Technologies

Initial release

1971

2010

2017

2009

Current release

6.0, February 2023

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache version 2, commercial enterprise edition

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++

Erlang

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

FreeBSD
Linux
macOS
Windows

Linux
OS X

Data scheme

yes

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

restricted

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

SQL-like query language

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

HTTP API
Native Erlang Interface

Supported programming languages

Natural

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

in Natural

user defined functions

in JavaScript

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Synchronous replication based on Galera library

selectable replication factor

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

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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)

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

Google Cloud Identity & Access Management (IAM)

yes, using Riak Security

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.