DBMS > Dgraph vs. Google BigQuery vs. Ingres vs. Transbase

System Properties Comparison Dgraph vs. Google BigQuery vs. Ingres vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Large scale data warehouse service with append-only tables

Well established RDBMS

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

Primary database model

Graph DBMS

Relational DBMS

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	4.67
Rank	#77	Overall
	#42	Relational DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

dgraph.io

cloud.google.com/bigquery

www.actian.com/databases/ingres

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

Technical documentation

dgraph.io/docs

cloud.google.com/bigquery/docs

docs.actian.com/ingres

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

Developer

Dgraph Labs, Inc.

Google

Actian Corporation

Transaction Software GmbH

Initial release

2016

2010

1974

originally developed at University Berkely in early 1970s

1987

Current release

11.2, May 2022

Transbase 8.3, 2022

License

Commercial or Open Source

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

C and C++

Server operating systems

Linux
OS X
Windows

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

yes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Ingres Replicator

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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.

User concepts

Access control

Planned for future releases

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

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.