DBMS > BaseX vs. Google BigQuery vs. Google Cloud Bigtable vs. Sqrrl

System Properties Comparison BaseX vs. Google BigQuery vs. Google Cloud Bigtable vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

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

Large scale data warehouse service with append-only tables

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Native XML DBMS

Relational DBMS

Key-value store
Wide column store

Document store
Graph DBMS
Key-value store
Wide column store

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	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Website

basex.org

cloud.google.com/bigquery

cloud.google.com/bigtable

sqrrl.com

Technical documentation

docs.basex.org

cloud.google.com/bigquery/docs

cloud.google.com/bigtable/docs

Developer

BaseX GmbH

Google

Amazon

originally Sqrrl Data, Inc.

Initial release

2007

2010

2015

2012

Current release

11.0, June 2024

License

Commercial or Open Source

Open Source

BSD license

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

Server operating systems

Linux
OS X
Windows

hosted

Linux

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

via events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

none

Internal replication in Colossus, and regional replication between two clusters in different zones

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

Transaction concepts

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

multiple readers, single writer

Since BigQuery is designed for querying data

Atomic single-row operations

Atomic updates per row, document, or graph entity

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)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.