DBMS > Google BigQuery vs. Greenplum vs. JaguarDB vs. Postgres-XL vs. Qdrant

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

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

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

A high-performance vector database with neural network or semantic-based matching

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Vector 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.53
Rank	#254	Overall
	#117	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

cloud.google.com/bigquery

greenplum.org

www.jaguardb.com

www.postgres-xl.org

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

cloud.google.com/bigquery/docs

docs.greenplum.org

www.jaguardb.com/support.html

www.postgres-xl.org/documentation

qdrant.tech/documentation

Developer

Google

Pivotal Software Inc.

DataJaguar, Inc.

Qdrant

Initial release

2010

2005

2015

2014

since 2012, originally named StormDB

2021

Current release

7.0.0, September 2023

3.3 July 2023

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL V3.0

Open Source

Mozilla public license

Open Source

Apache Version 2.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

C++

the server part. Clients available in other languages

Rust

Server operating systems

hosted

Linux

Linux
macOS

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

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

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

Collection-level replication

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

Eventual Consistency, tunable 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

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

fine grained access rights according to SQL-standard

Key-based authentication

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.