DBMS > Google BigQuery vs. IBM Cloudant vs. InfinityDB vs. JaguarDB vs. Tigris

System Properties Comparison Google BigQuery vs. IBM Cloudant vs. InfinityDB vs. JaguarDB vs. Tigris

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Database as a Service offering based on Apache CouchDB

A Java embedded Key-Value Store which extends the Java Map interface

Performant, highly scalable DBMS for AI and IoT applications

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Document store

Key-value store

Key-value store
Vector DBMS

Document store
Key-value store
Search engine
Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/cloudant

boilerbay.com

www.jaguardb.com

www.tigrisdata.com

Technical documentation

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

boilerbay.com/infinitydb/manual

www.jaguardb.com/support.html

www.tigrisdata.com/docs

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Boiler Bay Inc.

DataJaguar, Inc.

Tigris Data, Inc.

Initial release

2010

2002

2015

2022

Current release

4.0

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Apache Version 2.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

Erlang

Java

C++

the server part. Clients available in other languages

Server operating systems

hosted

All OS with a Java VM

Linux

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

RESTful HTTP/JSON API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

JDBC
ODBC

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

Java

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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

Since BigQuery is designed for querying data

atomic operations within a document possible

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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)

Access rights for users can be defined per database

rights management via user accounts

Access rights for users and roles

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.