DBMS > 4D vs. DataFS vs. GeoMesa vs. Google Cloud Bigtable

System Properties Comparison 4D vs. DataFS vs. GeoMesa vs. Google Cloud Bigtable

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Primary database model

Relational DBMS

Object oriented DBMS

Spatial DBMS

Key-value store
Wide column store

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	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Website

www.4d.com

newdatabase.com

www.geomesa.org

cloud.google.com/bigtable

Technical documentation

developer.4d.com

dev.mobiland.com/Overview.xsp

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

cloud.google.com/bigtable/docs

Developer

4D, Inc

Mobiland AG

CCRi and others

Google

Initial release

1984

2018

2014

2015

Current release

v20, April 2023

1.1.263, October 2022

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Server operating systems

OS X
Windows

Windows

hosted

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

schema-free

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

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

.NET Client API
Proprietary client DLL
WinRT client

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Supported programming languages

4D proprietary IDE
PHP

.Net
C
C#
C++
VB.Net

C#
C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

no, except callback-events from server when changes happened

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

Internal replication in Colossus, and regional replication between two clusters in different zones

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

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

User concepts

Access control

Users and groups

Windows-Profile

yes

depending on the DBMS used for storage

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

Google Launches Cloud Bigtable, A Highly Scalable And Performant NoSQL Database
6 May 2015, TechCrunch

provided by Google News

Share this page