DBMS > Adabas vs. Greenplum vs. Hazelcast vs. Snowflake vs. Sphinx

System Properties Comparison Adabas vs. Greenplum vs. Hazelcast vs. Snowflake vs. Sphinx

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A widely adopted in-memory data grid

Cloud-based data warehousing service for structured and semi-structured data

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store

JSON support with IMDG 3.12

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

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

Technical documentation

docs.greenplum.org

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Software AG

Pivotal Software Inc.

Hazelcast

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

1971

2005

2008

2014

2001

Current release

7.0.0, September 2023

5.3.6, November 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

All OS with a Java VM

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

since Version 4.2

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

SQL-like query language

yes

SQL-like query language (SphinxQL)

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
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

Natural

C
Java
Perl
Python
R

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

in Natural

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Source-replica replication

yes

Replicated Map

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

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 Sphinx index.

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)

fine grained access rights according to SQL-standard

Role-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.