DBMS > Google BigQuery vs. LevelDB vs. Quasardb vs. TimescaleDB vs. YottaDB

System Properties Comparison Google BigQuery vs. LevelDB vs. Quasardb vs. TimescaleDB vs. YottaDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Distributed, high-performance timeseries database

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A fast and solid embedded Key-value store

Primary database model

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	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

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

Website

cloud.google.com/bigquery

github.com/google/leveldb

quasar.ai

www.timescale.com

yottadb.com

Technical documentation

cloud.google.com/bigquery/docs

github.com/google/leveldb/blob/main/doc/index.md

doc.quasar.ai/master

docs.timescale.com

yottadb.com/resources/documentation

Developer

Google

quasardb

Timescale

YottaDB, LLC

Initial release

2010

2011

2009

2017

2001

Current release

1.23, February 2021

3.14.1, January 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

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

Open Source

Apache 2.0

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

C++

Server operating systems

hosted

Illumos
Linux
OS X
Windows

BSD
Linux
OS X
Windows

Linux
OS X
Windows

Docker
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

by using the Octo plugin

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with selectable replication factor

Source-replica replication with hot standby and reads on replicas

yes

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

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

by using LevelDB

yes

In-memory capabilities

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

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

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.