DBMS > Google BigQuery vs. JaguarDB vs. Microsoft Azure Table Storage vs. OrientDB vs. WakandaDB

System Properties Comparison Google BigQuery vs. JaguarDB vs. Microsoft Azure Table Storage vs. OrientDB vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Performant, highly scalable DBMS for AI and IoT applications

A Wide Column Store for rapid development using massive semi-structured datasets

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Wide column store

Document store
Graph DBMS
Key-value store

Object oriented DBMS

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	3.02
Rank	#88	Overall
	#16	Document stores
	#6	Graph DBMS
	#12	Key-value stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

cloud.google.com/bigquery

www.jaguardb.com

azure.microsoft.com/en-us/services/storage/tables

orientdb.org

wakanda.github.io

Technical documentation

cloud.google.com/bigquery/docs

www.jaguardb.com/support.html

www.orientdb.com/docs/last/index.html

wakanda.github.io/doc

Developer

Google

DataJaguar, Inc.

Microsoft

OrientDB LTD; CallidusCloud; SAP

Wakanda SAS

Initial release

2010

2015

2012

2010

2012

Current release

3.3 July 2023

3.2.29, March 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

Open Source

Apache version 2

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

C++

the server part. Clients available in other languages

Java

C++, JavaScript

Server operating systems

hosted

Linux

hosted

All OS with a Java JDK (>= JDK 6)

Linux
OS X
Windows

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language, no joins

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java, Javascript

yes

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

Access rights based on private key authentication or shared access signatures

Access rights for users and roles; record level security configurable

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.