DBMS > Google BigQuery vs. Infobright vs. Postgres-XL vs. VoltDB

System Properties Comparison Google BigQuery vs. Infobright vs. Postgres-XL vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

cloud.google.com/bigquery

ignitetech.com/softwarelibrary/infobrightdb

www.postgres-xl.org

www.voltdb.com

Technical documentation

cloud.google.com/bigquery/docs

www.postgres-xl.org/documentation

docs.voltdb.com

Developer

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

VoltDB Inc.

Initial release

2010

2005

2014

since 2012, originally named StormDB

2010

Current release

10 R1, October 2018

11.3, April 2022

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Mozilla public license

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

hosted

Linux
Windows

Linux
macOS

Linux
OS X

for development

Data scheme

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

XML type, but no XML query functionality

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

MVCC

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

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

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.