DBMS > Bangdb vs. Google BigQuery vs. RavenDB vs. Teradata Aster

System Properties Comparison Bangdb vs. Google BigQuery vs. RavenDB 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

Converged and high performance database for device data, events, time series, document and graph

Large scale data warehouse service with append-only tables

Open Source Operational and Transactional Enterprise NoSQL Document Database

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

bangdb.com

cloud.google.com/bigquery

ravendb.net

Technical documentation

docs.bangdb.com

cloud.google.com/bigquery/docs

ravendb.net/docs

Developer

Sachin Sinha, BangDB

Google

Hibernating Rhinos

Teradata

Initial release

2012

2010

2005

Current release

BangDB 2.0, October 2021

5.4, July 2022

License

Commercial or Open Source

Open Source

BSD 3

commercial

Open Source

AGPL version 3, commercial license available

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

C, C++

Server operating systems

Linux

hosted

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

schema-free

yes

schema-free

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: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

yes

SQL-like query language (RQL)

yes

APIs and other access methods

Proprietary protocol
RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
C++
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

R packages

Triggers

yes, Notifications (with Streaming only)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Multi-source replication

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

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, run db with in-memory only mode

User concepts

Access control

yes (enterprise version only)

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

Google Cloud Identity & Access Management (IAM)

Authorization levels configured per client per database

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.