DBMS > 4D vs. Apache Druid vs. Atos Standard Common Repository vs. SAP HANA vs. Tkrzw

System Properties Comparison 4D vs. Apache Druid vs. Atos Standard Common Repository vs. SAP HANA vs. Tkrzw

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Application development environment with integrated database management system

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

In-memory, column based data store. Available as appliance or cloud service

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Document store
Key-value store

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	0.09
Rank	#354	Overall
	#51	Key-value stores

Website

www.4d.com

druid.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.sap.com/products/hana.html

dbmx.net/tkrzw

Technical documentation

developer.4d.com

druid.apache.org/docs/latest/design

help.sap.com/hana

Developer

4D, Inc

Apache Software Foundation and contributors

Atos Convergence Creators

SAP

Mikio Hirabayashi

Initial release

1984

2012

2016

2010

2020

Current release

v20, April 2023

29.0.1, April 2024

1703

2.0 SPS07 (April 4, 2023), April 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

OS X
Windows

Linux
OS X
Unix

Linux

Appliance or cloud-service

Linux
macOS

Data scheme

yes

schema-less columns are supported

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

close to SQL 92

SQL for querying

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
RESTful HTTP/JSON API

LDAP

JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages with LDAP bindings

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

Sharding

cell division

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, via HDFS, S3 or other storage engines

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

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

using specific database classes

User concepts

Access control

Users and groups

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

LDAP bind authentication

yes

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.