DBMS > Google BigQuery vs. Lovefield vs. Stardog vs. YottaDB

System Properties Comparison Google BigQuery vs. Lovefield vs. Stardog vs. YottaDB

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

Embeddable relational database for web apps written in pure JavaScript

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Graph DBMS
RDF store

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

cloud.google.com/bigquery

google.github.io/lovefield

www.stardog.com

yottadb.com

Technical documentation

cloud.google.com/bigquery/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.stardog.com

yottadb.com/resources/documentation

Developer

Google

Stardog-Union

YottaDB, LLC

Initial release

2010

2014

2010

2001

Current release

2.1.12, February 2017

7.3.0, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

AGPL 3.0

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

JavaScript

Java

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
macOS
Windows

Docker
Linux

Data scheme

yes

schema-free and OWL/RDFS-schema support

schema-free

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

by using the Octo plugin

APIs and other access methods

RESTful HTTP/JSON API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

Using read-only observers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication in HA-Cluster

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

Users and groups based on OS-security mechanisms

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.