DBMS > 4D vs. Citus vs. CouchDB vs. Ehcache vs. SAP HANA

System Properties Comparison 4D vs. Citus vs. CouchDB vs. Ehcache vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A widely adopted Java cache with tiered storage options

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

Primary database model

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

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	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.sap.com/products/hana.html

Technical documentation

developer.4d.com

docs.citusdata.com

docs.couchdb.org/en/stable

www.ehcache.org/documentation

help.sap.com/hana

Developer

4D, Inc

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Terracotta Inc, owned by Software AG

SAP

Initial release

1984

2010

2005

2009

2010

Current release

v20, April 2023

8.1, December 2018

3.3.3, December 2023

3.10.0, March 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available

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

Erlang

Java

Server operating systems

OS X
Windows

Linux

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Appliance or cloud-service

Data scheme

yes

schema-free

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

close to SQL 92

yes

standard, with numerous extensions

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

JCache

JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java

Server-side scripts

Stored procedures

yes

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

View functions in JavaScript

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

Sharding

by using Terracotta Server

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single document possible

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Users and groups

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.