DBMS > ArcadeDB vs. Google BigQuery vs. Google Cloud Datastore vs. SAP Adaptive Server vs. STSdb

System Properties Comparison ArcadeDB vs. Google BigQuery vs. Google Cloud Datastore vs. SAP Adaptive Server vs. STSdb

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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	4.47
Rank	#76	Overall
	#12	Document stores

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

arcadedb.com

cloud.google.com/bigquery

cloud.google.com/datastore

www.sap.com/products/technology-platform/sybase-ase.html

github.com/STSSoft/STSdb4

Technical documentation

docs.arcadedb.com

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

help.sap.com/docs/SAP_ASE

Developer

Arcade Data

Google

SAP, Sybase

STS Soft SC

Initial release

2021

2010

2008

1987

2011

Current release

September 2021

16.0

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPLv2, commercial license available

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

All OS with a Java VM

hosted

AIX
HP-UX
Linux
Solaris
Unix
Windows

Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

SQL-like query language, no joins

yes

SQL-like query language (GQL)

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

.NET Client API

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
C++
Cobol
Java
Java
Perl
PHP
Python

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

Java and Transact-SQL

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.