DBMS > Google BigQuery vs. JanusGraph vs. Spark SQL vs. TerminusDB vs. Transbase

System Properties Comparison Google BigQuery vs. JanusGraph vs. Spark SQL vs. TerminusDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

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.02
Rank	#125	Overall
	#12	Graph DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

cloud.google.com/bigquery

janusgraph.org

spark.apache.org/sql

terminusdb.com

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/bigquery/docs

docs.janusgraph.org

spark.apache.org/docs/latest/sql-programming-guide.html

terminusdb.github.io/terminusdb/#

www.transaction.de/en/products/transbase/features.html

Developer

Google

Linux Foundation; originally developed as Titan by Aurelius

Apache Software Foundation

DataChemist Ltd.

Transaction Software GmbH

Initial release

2010

2017

2014

2018

1987

Current release

0.6.3, February 2023

3.5.0 ( 2.13), September 2023

11.0.0, January 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPL V3

commercial

free development license

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

Scala

Prolog, Rust

C and C++

Server operating systems

hosted

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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 DML and DDL statements

SQL-like query language (WOQL)

yes

APIs and other access methods

RESTful HTTP/JSON API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Clojure
Java
Python

Java
Python
R
Scala

JavaScript
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

yes, utilizing Spark Core

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Journaling Streams

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

in-memory journaling

yes

In-memory capabilities

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

User authentification and security via Rexster Graph Server

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.