DBMS > BigchainDB vs. EDB Postgres vs. FatDB vs. Google BigQuery

System Properties Comparison BigchainDB vs. EDB Postgres vs. FatDB vs. Google BigQuery

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

Primary database model

Document store

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

www.bigchaindb.com

www.enterprisedb.com

cloud.google.com/bigquery

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.enterprisedb.com/docs

cloud.google.com/bigquery/docs

Developer

EnterpriseDB

FatCloud

Google

Initial release

2016

2005

2012

2010

Current release

14, December 2021

License

Commercial or Open Source

Open Source

AGPL v3

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

Python

Server operating systems

Linux

Linux
Windows

Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

standard with numerous extensions

Via inetgration in SQL Server

yes

APIs and other access methods

CLI Client
RESTful HTTP API

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

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

yes

via applications

user defined functions

in JavaScript

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

by hash, list or range

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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

Google Cloud Identity & Access Management (IAM)

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.