DBMS > 4D vs. Google Cloud Datastore vs. InfinityDB vs. SAP HANA

System Properties Comparison 4D vs. Google Cloud Datastore vs. InfinityDB vs. SAP HANA

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A Java embedded Key-Value Store which extends the Java Map interface

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

Primary database model

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.47
Rank	#110	Overall
	#54	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.4d.com

cloud.google.com/datastore

boilerbay.com

www.sap.com/products/hana.html

Technical documentation

developer.4d.com

cloud.google.com/datastore/docs

boilerbay.com/infinitydb/manual

help.sap.com/hana

Developer

4D, Inc

Google

Boiler Bay Inc.

SAP

Initial release

1984

2008

2002

2010

Current release

v20, April 2023

4.0

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

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

hosted

All OS with a Java VM

Appliance or cloud-service

Data scheme

yes

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language (GQL)

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

Server-side scripts

Stored procedures

yes

using Google App Engine

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

User concepts

Access control

Users and groups

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

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.