DBMS > Google BigQuery vs. Hazelcast vs. Sqrrl vs. Transbase

System Properties Comparison Google BigQuery vs. Hazelcast vs. Sqrrl vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Adaptable, secure NoSQL built on Apache Accumulo

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

cloud.google.com/bigquery

hazelcast.com

sqrrl.com

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

www.transaction.de/en/products/transbase/features.html

Developer

Google

Hazelcast

Amazon

originally Sqrrl Data, Inc.

Transaction Software GmbH

Initial release

2010

2008

2012

1987

Current release

5.3.6, November 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

free development license

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

Server operating systems

hosted

All OS with a Java VM

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

selectable replication factor

making use of Hadoop

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Immediate Consistency

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

one or two-phase-commit; repeatable reads; read commited

Atomic updates per row, document, or graph entity

yes

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

fine grained access rights according to SQL-standard

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.