DBMS > Google BigQuery vs. Lovefield vs. Quasardb vs. TimesTen vs. WakandaDB

System Properties Comparison Google BigQuery vs. Lovefield vs. Quasardb vs. TimesTen vs. WakandaDB

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

Distributed, high-performance timeseries database

In-Memory RDBMS compatible to Oracle

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

cloud.google.com/bigquery

google.github.io/lovefield

quasar.ai

www.oracle.com/database/technologies/related/timesten.html

wakanda.github.io

Technical documentation

cloud.google.com/bigquery/docs

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

doc.quasar.ai/master

docs.oracle.com/database/timesten-18.1

wakanda.github.io/doc

Developer

Google

quasardb

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Wakanda SAS

Initial release

2010

2014

2009

1998

2012

Current release

2.1.12, February 2017

3.14.1, January 2024

11 Release 2 (11.2.2.8.0)

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Open Source

AGPLv3, extended commercial license available

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

C++

C++, JavaScript

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

BSD
Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

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

C
C++
Java
PL/SQL

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

PL/SQL

yes

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with selectable replication factor

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

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

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

yes

by using LevelDB

yes

by means of logfiles and checkpoints

yes

In-memory capabilities

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

yes

using MemoryDB

yes

Transient mode

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Cryptographically strong user authentication and audit trail

fine grained access rights according to SQL-standard

yes

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.