DBMS > Google BigQuery vs. HyperSQL vs. TerminusDB vs. TinkerGraph

System Properties Comparison Google BigQuery vs. HyperSQL vs. TerminusDB vs. TinkerGraph

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

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

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

Primary database model

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

cloud.google.com/bigquery

hsqldb.org

terminusdb.com

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

Technical documentation

cloud.google.com/bigquery/docs

hsqldb.org/web/hsqlDocsFrame.html

terminusdb.github.io/terminusdb/#

Developer

Google

DataChemist Ltd.

Initial release

2010

2001

2018

2009

Current release

2.7.2, June 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

based on BSD license

Open Source

GPL V3

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

Prolog, Rust

Java

Server operating systems

hosted

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Linux

Data scheme

yes

schema-free

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 (WOQL)

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

JDBC via HTTP
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

TinkerPop 3

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC
Java

JavaScript
Python

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java, SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Journaling Streams

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

in-memory journaling

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)

fine grained access rights according to SQL-standard

Role-based access control

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.