DBMS > 4D vs. Apache Drill vs. Atos Standard Common Repository vs. BaseX vs. SAP HANA

System Properties Comparison 4D vs. Apache Drill vs. Atos Standard Common Repository vs. BaseX vs. SAP HANA

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

Primary database model

Relational DBMS

Document store
Relational DBMS

Document store
Key-value store

Native XML DBMS

Relational DBMS

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.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.4d.com

drill.apache.org

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

basex.org

www.sap.com/products/hana.html

Technical documentation

developer.4d.com

drill.apache.org/docs

docs.basex.org

help.sap.com/hana

Developer

4D, Inc

Apache Software Foundation

Atos Convergence Creators

BaseX GmbH

SAP

Initial release

1984

2012

2016

2007

2010

Current release

v20, April 2023

1.20.3, January 2023

1703

10.7, August 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

BSD license

commercial

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

Server operating systems

OS X
Windows

Linux
OS X
Windows

Linux

Linux
OS X
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

XQuery supports types

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 SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC
RESTful HTTP API

LDAP

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

C++

All languages with LDAP bindings

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

Server-side scripts

Stored procedures

yes

user defined functions

yes

SQLScript, R

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Users and groups

Depending on the underlying data source

LDAP bind authentication

Users with fine-grained authorization concept on 4 levels

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.