DBMS > 4D vs. DataFS vs. GeoMesa vs. GridGain

System Properties Comparison 4D vs. DataFS vs. GeoMesa vs. GridGain

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

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.

GridGain is an in-memory computing platform, built on Apache Ignite

Primary database model

Relational DBMS

Object oriented DBMS

Spatial DBMS

Key-value store
Relational 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	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Website

Technical documentation

developer.4d.com

dev.mobiland.com/Overview.xsp

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

www.gridgain.com/docs/index.html

Developer

4D, Inc

Mobiland AG

CCRi and others

GridGain Systems, Inc.

Initial release

1984

2018

2014

2007

Current release

v20, April 2023

1.1.263, October 2022

5.0.0, May 2024

GridGain 8.5.1

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

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

Scala

Java, C++, .Net

Server operating systems

OS X
Windows

Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

.NET Client API
Proprietary client DLL
WinRT client

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

4D proprietary IDE
PHP

.Net
C
C#
C++
VB.Net

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

no, except callback-events from server when changes happened

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

Proprietary Sharding system

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

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.

depending on storage layer

yes

User concepts

Access control

Users and groups

Windows-Profile

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks and Files

GridGain's 2023 Growth Positions Company for Strong 2024
24 January 2024, PR Newswire

GridGain Unified Real-Time Data Platform Version 8.9 Addresses Today's More Complex Real-Time Data Processing ...
12 October 2023, GlobeNewswire

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain: Product Overview and Analysis
5 June 2019, eWeek

provided by Google News

Share this page