DBMS > Google BigQuery vs. jBASE vs. Postgres-XL vs. Teradata Aster

System Properties Comparison Google BigQuery vs. jBASE vs. Postgres-XL vs. Teradata Aster

Please select another system to include it in the comparison.

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.

Description

Large scale data warehouse service with append-only tables

A robust multi-value DBMS comprising development tools and middleware

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

cloud.google.com/bigquery

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.postgres-xl.org

Technical documentation

cloud.google.com/bigquery/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

www.postgres-xl.org/documentation

Developer

Google

Rocket Software (formerly Zumasys)

Teradata

Initial release

2010

1991

2014

since 2012, originally named StormDB

2005

Current release

5.7

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Mozilla public 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

Server operating systems

hosted

AIX
Linux
Windows

Linux
macOS

Linux

Data scheme

yes

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

Typing

predefined data types such as float or date

yes

optional

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

XML type, but no XML query functionality

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

yes

distributed, parallel query execution

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

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

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

MVCC

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

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

Google Cloud Identity & Access Management (IAM)

Access rights can be defined down to the item level

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.