DBMS > 4D vs. AlaSQL vs. Amazon DynamoDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB

System Properties Comparison 4D vs. AlaSQL vs. Amazon DynamoDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

JavaScript DBMS library

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

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Relational DBMS

Document store
Key-value store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.4d.com

alasql.org

aws.amazon.com/dynamodb

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

Technical documentation

developer.4d.com

github.com/AlaSQL/alasql

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

Developer

4D, Inc

Andrey Gershun & Mathias R. Wulff

Amazon

Google

Microsoft

Initial release

1984

2014

2012

2008

2014

Current release

v20, April 2023

License

Commercial or Open Source

commercial

Open Source

MIT-License

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

JavaScript

Server operating systems

OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

close to SQL 92

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JavaScript API

RESTful HTTP API

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

4D proprietary IDE
PHP

JavaScript

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

using Google App Engine

JavaScript

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

can be specified for read operations

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.

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

yes

only for local storage and DOM-storage

ACID

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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)

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

Access rights can be defined down to the item level

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.