DBMS > Adabas vs. ClickHouse vs. Datomic vs. Google Cloud Datastore vs. Percona Server for MongoDB

System Properties Comparison Adabas vs. ClickHouse vs. Datomic vs. Google Cloud Datastore vs. Percona Server for MongoDB

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 high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Multivalue DBMS

Relational DBMS

Document store

Secondary database models

Time Series DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

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

clickhouse.com

www.datomic.com

cloud.google.com/datastore

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

clickhouse.com/docs

docs.datomic.com

cloud.google.com/datastore/docs

docs.percona.com/percona-distribution-for-mongodb

Developer

Software AG

Clickhouse Inc.

Cognitect

Google

Percona

Initial release

1971

2016

2012

2008

2015

Current release

v24.4.1.2088-stable, May 2024

1.0.6735, June 2023

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

limited edition free

commercial

Open Source

GPL Version 2

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

Java, Clojure

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

FreeBSD
Linux
macOS

All OS with a Java VM

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (GQL)

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

proprietary protocol using JSON

Supported programming languages

Natural

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

Clojure
Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

in Natural

yes

Transaction Functions

using Google App Engine

JavaScript

Triggers

By using transaction functions

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

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

key based and custom

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

none

But extensive use of caching in the application peers

Multi-source replication using Paxos

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

via In-Memory Engine

User concepts

Access control

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

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users and roles

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.