DBMS > Google BigQuery vs. OrigoDB vs. TerminusDB vs. XTDB

System Properties Comparison Google BigQuery vs. OrigoDB vs. TerminusDB vs. XTDB

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 fully ACID in-memory object graph database

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store
Object oriented 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

cloud.google.com/bigquery

origodb.com

terminusdb.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

cloud.google.com/bigquery/docs

origodb.com/docs

terminusdb.github.io/terminusdb/#

www.xtdb.com/docs

Developer

Google

Robert Friberg et al

DataChemist Ltd.

Juxt Ltd.

Initial release

2010

2009

under the name LiveDB

2018

2019

Current release

11.0.0, January 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

MIT 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

Prolog, Rust

Clojure

Server operating systems

hosted

Linux
Windows

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

yes, extensible-data-notation format

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

HTTP REST
JDBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net

JavaScript
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Journaling Streams

yes, each node contains all data

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

depending on model

yes

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

Write ahead log

yes

in-memory journaling

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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)

Role based authorization

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.