DBMS > Apache Drill vs. EDB Postgres vs. Google BigQuery vs. Postgres-XL

System Properties Comparison Apache Drill vs. EDB Postgres vs. Google BigQuery vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

drill.apache.org

www.enterprisedb.com

cloud.google.com/bigquery

www.postgres-xl.org

Technical documentation

drill.apache.org/docs

www.enterprisedb.com/docs

cloud.google.com/bigquery/docs

www.postgres-xl.org/documentation

Developer

Apache Software Foundation

EnterpriseDB

Google

Initial release

2012

2005

2010

2014

since 2012, originally named StormDB

Current release

1.20.3, January 2023

14, December 2021

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

BSD for PostgreSQL-components

commercial

Open Source

Mozilla public license

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
OS X
Windows

Linux
Windows

hosted

Linux
macOS

Data scheme

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

standard with numerous extensions

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

RESTful HTTP/JSON API

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

Supported programming languages

C++

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

by hash, list or range

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

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)

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.