DBMS > EsgynDB vs. Google BigQuery vs. TerminusDB vs. ToroDB

System Properties Comparison EsgynDB vs. Google BigQuery vs. TerminusDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Large scale data warehouse service with append-only tables

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Graph DBMS

Document store

Secondary database models

Document store
RDF store

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

www.esgyn.cn

cloud.google.com/bigquery

terminusdb.com

github.com/torodb/server

Technical documentation

cloud.google.com/bigquery/docs

terminusdb.github.io/terminusdb/#

Developer

Esgyn

Google

DataChemist Ltd.

8Kdata

Initial release

2015

2010

2018

2016

Current release

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

AGPL-V3

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++, Java

Prolog, Rust

Java

Server operating systems

Linux

hosted

Linux

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Journaling Streams

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

Eventual Consistency
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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

Access rights for users and roles

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.