DBMS > Google BigQuery vs. HugeGraph vs. Spark SQL vs. Transbase

System Properties Comparison Google BigQuery vs. HugeGraph vs. Spark SQL vs. Transbase

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

A fast-speed and highly-scalable Graph DBMS

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

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

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.15
Rank	#339	Overall
	#33	Graph DBMS

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

cloud.google.com/bigquery

github.com/hugegraph
hugegraph.apache.org

spark.apache.org/sql

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

Technical documentation

cloud.google.com/bigquery/docs

hugegraph.apache.org/docs

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

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

Developer

Google

Baidu

Apache Software Foundation

Transaction Software GmbH

Initial release

2010

2018

2014

1987

Current release

0.9

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

C and C++

Server operating systems

hosted

Linux
macOS
Unix

Linux
OS X
Windows

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

also supports composite index and range index

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP/JSON API

Java API
RESTful HTTP API
TinkerPop Gremlin

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Groovy
Java
Python

Java
Python
R
Scala

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

asynchronous Gremlin script jobs

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on used storage backend, e.g. Cassandra and HBase

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

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

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)

Users, roles and permissions

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.