DBMS > Adabas vs. GeoSpock vs. HEAVY.AI vs. Lovefield vs. RocksDB

System Properties Comparison Adabas vs. GeoSpock vs. HEAVY.AI vs. Lovefield vs. RocksDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

used typically together with the Natural programming platform

Spatial and temporal data processing engine for extreme data scale

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Embeddable relational database for web apps written in pure JavaScript

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Multivalue DBMS

Relational DBMS

Key-value store

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

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

geospock.com

github.com/heavyai/heavydb
www.heavy.ai

google.github.io/lovefield

rocksdb.org

Technical documentation

docs.heavy.ai

github.com/google/lovefield/blob/master/docs/spec_index.md

github.com/facebook/rocksdb/wiki

Developer

Software AG

GeoSpock

HEAVY.AI, Inc.

Google

Facebook, Inc.

Initial release

1971

2016

2014

2013

Current release

2.0, September 2019

5.10, January 2022

2.1.12, February 2017

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

BSD

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

Java, Javascript

C++ and CUDA

JavaScript

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

Data scheme

yes

schema-free

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

temporal, categorical

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

ANSI SQL for query only (using Presto)

yes

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

JDBC

JDBC
ODBC
Thrift
Vega

C++ API
Java API

Supported programming languages

Natural

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

in Natural

Triggers

Using read-only observers

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

Round robin

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication

none

yes

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

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

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 table

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.