DBMS > 4D vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. TigerGraph

System Properties Comparison 4D vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. TigerGraph

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Application development environment with integrated database management system

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Graph DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

www.4d.com

aws.amazon.com/dynamodb

atos.net/en/convergence-creators/portfolio/standard-common-repository

cloud.google.com/datastore

www.tigergraph.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

docs.tigergraph.com

Developer

4D, Inc

Amazon

Atos Convergence Creators

Google

Initial release

1984

2012

2016

2008

2017

Current release

v20, April 2023

1703

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

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

Java

C++

Server operating systems

OS X
Windows

hosted

Linux

hosted

Linux

Data scheme

yes

schema-free

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

yes, details here

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

SQL-like query language (GQL)

SQL-like query language (GSQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

LDAP

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

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

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

C++
Java

Server-side scripts

Stored procedures

yes

using Google App Engine

yes

Triggers

yes

by integration with AWS Lambda

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

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.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

Atomic execution of specific operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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 and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

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

Role-based access control

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.