DBMS > EDB Postgres vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. Trafodion

System Properties Comparison EDB Postgres vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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.

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

Globally distributed, horizontally scalable, multi-model database service

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	1.91
Rank	#130	Overall
	#60	Relational DBMS

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.enterprisedb.com

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

trafodion.apache.org

Technical documentation

www.enterprisedb.com/docs

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

trafodion.apache.org/documentation.html

Developer

EnterpriseDB

Google

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2005

2008

2014

Current release

14, December 2021

2.3.0, February 2019

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

commercial

Open Source

Apache 2.0

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

C++, Java

Server operating systems

Linux
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

JSON types

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

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

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

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

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

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

ADO.NET
JDBC
ODBC

Supported programming languages

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

.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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

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

using Google App Engine

JavaScript

Java Stored Procedures

Triggers

yes

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

by hash, list or range

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

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.

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

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

fine grained access rights according to SQL-standard

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.