DBMS > ArcadeDB vs. Google BigQuery vs. Heroic vs. RocksDB

System Properties Comparison ArcadeDB vs. Google BigQuery vs. Heroic vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

Large scale data warehouse service with append-only tables

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Time Series DBMS

Key-value store

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

Score	0.02
Rank	#366	Overall
	#50	Document stores
	#38	Graph DBMS
	#53	Key-value stores
	#36	Time Series DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

arcadedb.com

cloud.google.com/bigquery

github.com/spotify/heroic

rocksdb.org

Technical documentation

docs.arcadedb.com

cloud.google.com/bigquery/docs

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

Arcade Data

Google

Spotify

Facebook, Inc.

Initial release

2021

2010

2014

2013

Current release

September 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Open Source

BSD

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

All OS with a Java VM

hosted

Linux

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

SQL-like query language, no joins

yes

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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)

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.