DBMS > Google BigQuery vs. LevelDB vs. Quasardb vs. RavenDB vs. TerminusDB

System Properties Comparison Google BigQuery vs. LevelDB vs. Quasardb vs. RavenDB vs. TerminusDB

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

cloud.google.com/bigquery

github.com/google/leveldb

quasar.ai

ravendb.net

terminusdb.com

Technical documentation

cloud.google.com/bigquery/docs

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

doc.quasar.ai/master

ravendb.net/docs

terminusdb.github.io/terminusdb/#

Developer

Google

quasardb

Hibernating Rhinos

DataChemist Ltd.

Initial release

2010

2011

2009

2010

2018

Current release

1.23, February 2021

3.14.1, January 2024

5.4, July 2022

11.0.0, January 2023

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

AGPL version 3, commercial license available

Open Source

GPL 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++

Prolog, Rust

Server operating systems

hosted

Illumos
Linux
OS X
Windows

BSD
Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

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

SQL-like query language (RQL)

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with selectable replication factor

Multi-source replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

ACID

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 journaling

In-memory capabilities

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

yes

Transient mode

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

Authorization levels configured per client per database

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.