DBMS > Google BigQuery vs. RavenDB vs. TerminusDB vs. TimesTen

System Properties Comparison Google BigQuery vs. RavenDB vs. TerminusDB vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Open Source Operational and Transactional Enterprise NoSQL Document Database

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

In-Memory RDBMS compatible to Oracle

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

cloud.google.com/bigquery

ravendb.net

terminusdb.com

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

Technical documentation

cloud.google.com/bigquery/docs

ravendb.net/docs

terminusdb.github.io/terminusdb/#

docs.oracle.com/database/timesten-18.1

Developer

Google

Hibernating Rhinos

DataChemist Ltd.

Oracle, TimesTen Performance Software, HP

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

Initial release

2010

2018

1998

Current release

5.4, July 2022

11.0.0, January 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

yes

SQL-like query language (RQL)

SQL-like query language (WOQL)

yes

APIs and other access methods

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

JavaScript
Python

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Journaling Streams

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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)

Authorization levels configured per client per database

Role-based access control

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.