DBMS > EDB Postgres vs. Google BigQuery vs. Google Cloud Datastore vs. YottaDB

System Properties Comparison EDB Postgres vs. Google BigQuery vs. Google Cloud Datastore vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Large scale data warehouse service with append-only tables

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

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Document store

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	1.91
Rank	#130	Overall
	#60	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.enterprisedb.com

cloud.google.com/bigquery

cloud.google.com/datastore

yottadb.com

Technical documentation

www.enterprisedb.com/docs

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

yottadb.com/resources/documentation

Developer

EnterpriseDB

Google

YottaDB, LLC

Initial release

2005

2010

2008

2001

Current release

14, December 2021

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

commercial

Open Source

AGPL 3.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

Server operating systems

Linux
Windows

hosted

Docker
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

yes

standard with numerous extensions

yes

SQL-like query language (GQL)

by using the Octo plugin

APIs and other access methods

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

RESTful HTTP/JSON API

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

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

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

user defined functions

in JavaScript

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

by hash, list or range

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

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.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

optimistic locking

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.

yes

User concepts

Access control

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users and groups based on OS-security mechanisms

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.