DBMS > 4D vs. Apache Phoenix vs. DataFS vs. GeoMesa

System Properties Comparison 4D vs. Apache Phoenix vs. DataFS vs. GeoMesa

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A scale-out RDBMS with evolutionary schema built on Apache HBase

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Primary database model

Relational DBMS

Object oriented DBMS

Spatial DBMS

Secondary database models

Graph DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Website

Technical documentation

developer.4d.com

phoenix.apache.org

dev.mobiland.com/Overview.xsp

www.geomesa.org/documentation/stable/user/index.html

Developer

4D, Inc

Apache Software Foundation

Mobiland AG

CCRi and others

Initial release

1984

2014

2018

2014

Current release

v20, April 2023

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

1.1.263, October 2022

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Scala

Server operating systems

OS X
Windows

Linux
Unix
Windows

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC

.NET Client API
Proprietary client DLL
WinRT client

Supported programming languages

4D proprietary IDE
PHP

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
C
C#
C++
VB.Net

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

no, except callback-events from server when changes happened

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Proprietary Sharding system

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

depending on storage layer

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

depending on storage layer

User concepts

Access control

Users and groups

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Windows-Profile

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Supercharge SQL on Your Data in Apache HBase with Apache Phoenix | Amazon Web Services
2 June 2016, AWS Blog

Bridge the SQL-NoSQL gap with Apache Phoenix
4 February 2016, InfoWorld

Apache Calcite, FreeMarker, Gora, Phoenix, and Solr updated
27 March 2017, SDTimes.com

Azure HDInsight Analytics Platform Now Supports Apache Hadoop 3.0
18 April 2019, eWeek

Deep dive into Azure HDInsight 4.0
25 September 2018, azure.microsoft.com

provided by Google News

Share this page