DBMS > Google BigQuery vs. jBASE vs. RavenDB vs. Realm vs. SWC-DB

System Properties Comparison Google BigQuery vs. jBASE vs. RavenDB vs. Realm vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A robust multi-value DBMS comprising development tools and middleware

Open Source Operational and Transactional Enterprise NoSQL Document Database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series 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	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

cloud.google.com/bigquery

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

ravendb.net

realm.io

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

cloud.google.com/bigquery/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

ravendb.net/docs

realm.io/docs

Developer

Google

Rocket Software (formerly Zumasys)

Hibernating Rhinos

Realm, acquired by MongoDB in May 2019

Alex Kashirin

Initial release

2010

1991

2010

2014

2020

Current release

5.7

5.4, July 2022

0.5, April 2021

License

Commercial or Open Source

commercial

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

Server operating systems

hosted

AIX
Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Android
Backend: server-less
iOS
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

yes

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

SQL-like query language (RQL)

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based 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

Proprietary protocol
Thrift

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C++

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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.

Immediate Consistency

Foreign keys

Referential integrity

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

In-memory capabilities

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

yes

In-Memory realm

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Access rights can be defined down to the item level

Authorization levels configured per client per database

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.