DBMS > BaseX vs. Google BigQuery vs. Teradata Aster vs. Warp 10 vs. Yaacomo

System Properties Comparison BaseX vs. Google BigQuery vs. Teradata Aster vs. Warp 10 vs. Yaacomo

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Yaacomo seems to be discontinued and is 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

Platform for big data analytics on multistructured data sources and types

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

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.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

basex.org

cloud.google.com/bigquery

www.warp10.io

yaacomo.com

Technical documentation

docs.basex.org

cloud.google.com/bigquery/docs

www.warp10.io/content/02_Getting_started

Developer

BaseX GmbH

Google

Teradata

SenX

Q2WEB GmbH

Initial release

2007

2010

2005

2015

2009

Current release

10.7, August 2023

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

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

Server operating systems

Linux
OS X
Windows

hosted

Linux

Linux
OS X
Windows

Android
Linux
Windows

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

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

ADO.NET
JDBC
ODBC
OLE DB

HTTP API
Jupyter
WebSocket

JDBC
ODBC

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#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

R packages

yes

WarpScript

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

selectable replication factor

based on HBase

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

based on HBase

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

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

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)

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

fine grained access rights according to SQL-standard

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.