DBMS > Adabas vs. Dolt vs. Geode vs. Microsoft Azure AI Search vs. Snowflake

System Properties Comparison Adabas vs. Dolt vs. Geode vs. Microsoft Azure AI Search vs. Snowflake

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 MySQL compatible DBMS with Git-like versioning of data and schema

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Search-as-a-service for web and mobile app development

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

Primary database model

Secondary database models

Document store

Vector DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	5.52
Rank	#59	Overall
	#6	Search engines

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

github.com/dolthub/dolt
www.dolthub.com

geode.apache.org

azure.microsoft.com/en-us/services/search

www.snowflake.com

Technical documentation

docs.dolthub.com

geode.apache.org/docs

learn.microsoft.com/en-us/azure/search

docs.snowflake.net/manuals/index.html

Developer

Software AG

DoltHub Inc

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

Snowflake Computing Inc.

Initial release

1971

2018

2002

2015

2014

Current release

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
macOS
Windows

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Data scheme

yes

schema-free

yes

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

SQL-like query language (OQL)

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

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Natural

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

yes

currently in alpha release

user defined functions

Triggers

yes

Cache Event Listeners

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

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

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

Only one user is configurable, and must be specified in the config file at startup

Access rights per client and object definable

yes

using Azure authentication

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.