DBMS > 4D vs. EDB Postgres vs. Google BigQuery vs. Microsoft Azure Cosmos DB

System Properties Comparison 4D vs. EDB Postgres vs. Google BigQuery vs. Microsoft Azure Cosmos DB

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

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

Large scale data warehouse service with append-only tables

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	1.91
Rank	#130	Overall
	#60	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Website

www.4d.com

www.enterprisedb.com

cloud.google.com/bigquery

azure.microsoft.com/services/cosmos-db

Technical documentation

developer.4d.com

www.enterprisedb.com/docs

cloud.google.com/bigquery/docs

learn.microsoft.com/azure/cosmos-db

Developer

4D, Inc

EnterpriseDB

Google

Microsoft

Initial release

1984

2005

2010

2014

Current release

v20, April 2023

14, December 2021

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

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

Server operating systems

OS X
Windows

Linux
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

close to SQL 92

yes

standard with numerous extensions

yes

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

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

Supported programming languages

4D proprietary IDE
PHP

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

.Net
Java
JavaScript
Objective-C
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

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

by hash, list or range

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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.

User concepts

Access control

Users and groups

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & 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.