DBMS > BaseX vs. Google BigQuery vs. MySQL vs. ReductStore

System Properties Comparison BaseX vs. Google BigQuery vs. MySQL 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.

Large scale data warehouse service with append-only tables

Widely used open source RDBMS

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

Key/Value like access via memcached API

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	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.05
Rank	#384	Overall
	#44	Time Series DBMS

Website

basex.org

cloud.google.com/bigquery

www.mysql.com

github.com/reductstore
www.reduct.store

Technical documentation

docs.basex.org

cloud.google.com/bigquery/docs

dev.mysql.com/doc

www.reduct.store/docs

Developer

BaseX GmbH

Google

Oracle

since 2010, originally MySQL AB, then Sun

ReductStore LLC

Initial release

2007

2010

1995

2023

Current release

10.7, August 2023

8.4.0, April 2024

1.9, March 2024

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

C++, Rust

Server operating systems

Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native 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
Java
JavaScript
Objective-C
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

not for MyISAM storage engine

Transaction concepts

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

multiple readers, single writer

Since BigQuery is designed for querying data

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept on 4 levels

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

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.