DBMS > BigObject vs. Google BigQuery vs. GridDB vs. TimesTen

System Properties Comparison BigObject vs. Google BigQuery vs. GridDB vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Large scale data warehouse service with append-only tables

Scalable in-memory time series database optimized for IoT and Big Data

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

bigobject.io

cloud.google.com/bigquery

griddb.net

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.bigobject.io

cloud.google.com/bigquery/docs

docs.griddb.net

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

BigObject, Inc.

Google

Toshiba Corporation

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2015

2010

2013

1998

Current release

5.1, August 2022

Release 22.1

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also 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++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Linux

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL-like DML and DDL statements

yes

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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 for users can be defined 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.