DBMS > Google BigQuery vs. Greenplum vs. JaguarDB vs. Machbase Neo vs. Postgres-XL

System Properties Comparison Google BigQuery vs. Greenplum vs. JaguarDB vs. Machbase Neo vs. Postgres-XL

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Performant, highly scalable DBMS for AI and IoT applications

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Website

cloud.google.com/bigquery

Technical documentation

cloud.google.com/bigquery/docs

docs.greenplum.org

www.jaguardb.com/support.html

machbase.com/dbms

www.postgres-xl.org/documentation

Developer

Google

Pivotal Software Inc.

DataJaguar, Inc.

Machbase

Initial release

2010

2005

2015

2013

2014

since 2012, originally named StormDB

Current release

7.0.0, September 2023

3.3 July 2023

V8.0, August 2023

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL V3.0

commercial

free test version available

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

C++

the server part. Clients available in other languages

Server operating systems

hosted

Linux

Linux
macOS
Windows

Linux
macOS

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

since Version 4.2

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Java
Perl
Python
R

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

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

volatile and lookup table

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

rights management via user accounts

simple password-based access control

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.