DBMS > Google BigQuery vs. GridGain vs. Rockset vs. Teradata Aster vs. TinkerGraph

System Properties Comparison Google BigQuery vs. GridGain vs. Rockset vs. Teradata Aster vs. TinkerGraph

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

GridGain is an in-memory computing platform, built on Apache Ignite

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Platform for big data analytics on multistructured data sources and types

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store

Relational DBMS

Graph DBMS

Secondary database models

Relational DBMS
Search engine

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	0.84
Rank	#209	Overall
	#35	Document stores

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

cloud.google.com/bigquery

www.gridgain.com

rockset.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

docs.rockset.com

Developer

Google

GridGain Systems, Inc.

Rockset

Teradata

Initial release

2010

2007

2019

2005

2009

Current release

GridGain 8.5.1

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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++, .Net

C++

Java

Server operating systems

hosted

Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

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

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

yes

in Aster File Store

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

Read-only SQL queries, including JOINs

yes

APIs and other access methods

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP REST

ADO.NET
JDBC
ODBC
OLE DB

TinkerPop 3

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

R packages

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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)

Security Hooks for custom implementations

Access rights for users and organizations can be defined via Rockset console

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.