DBMS > BaseX vs. Google BigQuery vs. JaguarDB vs. Microsoft Azure SQL Database vs. Microsoft Azure Table Storage

System Properties Comparison BaseX vs. Google BigQuery vs. JaguarDB vs. Microsoft Azure SQL Database vs. Microsoft Azure Table Storage

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

Performant, highly scalable DBMS for AI and IoT applications

Database as a Service offering with high compatibility to Microsoft SQL Server

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Native XML DBMS

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Wide column store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Website

basex.org

cloud.google.com/bigquery

www.jaguardb.com

azure.microsoft.com/en-us/products/azure-sql/database

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

docs.basex.org

cloud.google.com/bigquery/docs

www.jaguardb.com/support.html

docs.microsoft.com/en-us/azure/azure-sql

Developer

BaseX GmbH

Google

DataJaguar, Inc.

Microsoft

Initial release

2007

2010

2015

2010

2012

Current release

10.7, August 2023

3.3 July 2023

V12

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

GPL V3.0

commercial

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

the server part. Clients available in other languages

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

hosted

Data scheme

schema-free

yes

schema-free

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
ODBC

RESTful 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

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Transact SQL

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes, with always 3 replicas available

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

MapReduce

Offers an API for user-defined Map/Reduce methods

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

multiple readers, single writer

Since BigQuery is designed for querying data

ACID

optimistic locking

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.

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)

rights management via user accounts

fine grained access rights according to SQL-standard

Access rights based on private key authentication or shared access signatures

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.