DBMS > atoti vs. Google BigQuery vs. Hazelcast vs. SiriDB

System Properties Comparison atoti vs. Google BigQuery vs. Hazelcast vs. SiriDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Open Source Time Series DBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.45
Rank	#253	Overall
	#13	Object oriented DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Website

atoti.io

cloud.google.com/bigquery

hazelcast.com

siridb.com

Technical documentation

docs.atoti.io

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

docs.siridb.com

Developer

ActiveViam

Google

Hazelcast

Cesbit

Initial release

2010

2008

2017

Current release

5.3.6, November 2023

License

Commercial or Open Source

commercial

free versions available

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

MIT 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

Server operating systems

hosted

All OS with a Java VM

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

Multidimensional Expressions (MDX)

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

Python

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

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

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

simple rights management via user accounts

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.