DBMS > BaseX vs. EDB Postgres vs. Google BigQuery vs. ReductStore

System Properties Comparison BaseX vs. EDB Postgres vs. Google BigQuery vs. ReductStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

Primary database model

Native XML DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	1.91
Rank	#130	Overall
	#60	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.05
Rank	#384	Overall
	#44	Time Series DBMS

Website

basex.org

www.enterprisedb.com

cloud.google.com/bigquery

github.com/reductstore
www.reduct.store

Technical documentation

docs.basex.org

www.enterprisedb.com/docs

cloud.google.com/bigquery/docs

www.reduct.store/docs

Developer

BaseX GmbH

EnterpriseDB

Google

ReductStore LLC

Initial release

2007

2005

2010

2023

Current release

11.0, June 2024

14, December 2021

1.9, March 2024

License

Commercial or Open Source

Open Source

BSD license

commercial

BSD for PostgreSQL-components

commercial

Open Source

Business Source License 1.1

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++, Rust

Server operating systems

Linux
OS X
Windows

Linux
Windows

hosted

Docker
Linux
macOS
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

XQuery supports types

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

yes

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

RESTful HTTP/JSON API

HTTP API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions

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

user defined functions

in JavaScript

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

by hash, list or range

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source 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

Transaction concepts

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

multiple readers, single writer

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

In-memory capabilities

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

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

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)

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.