DBMS > Google BigQuery vs. InfinityDB vs. RavenDB vs. searchxml

System Properties Comparison Google BigQuery vs. InfinityDB vs. RavenDB vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Key-value store

Document store

Native XML DBMS
Search engine

Secondary database models

Graph DBMS
Spatial DBMS
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	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

cloud.google.com/bigquery

boilerbay.com

ravendb.net

www.searchxml.net/category/products

Technical documentation

cloud.google.com/bigquery/docs

boilerbay.com/infinitydb/manual

ravendb.net/docs

www.searchxml.net/support/handouts

Developer

Google

Boiler Bay Inc.

Hibernating Rhinos

informationpartners gmbh

Initial release

2010

2002

2010

2015

Current release

4.0

5.4, July 2022

1.0

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

commercial

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

Java

C++

Server operating systems

hosted

All OS with a Java VM

Linux
macOS
Raspberry Pi
Windows

Windows

Data scheme

yes

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

schema-free

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.

yes

Secondary indexes

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

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

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)

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

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

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.

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID, Cluster-wide transaction available

multiple readers, single writer

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)

Authorization levels configured per client per database

Domain, group and role-based access control at the document level and for application services

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.