DBMS > ArcadeDB vs. Atos Standard Common Repository vs. dBASE vs. Google BigQuery

System Properties Comparison ArcadeDB vs. Atos Standard Common Repository vs. dBASE vs. Google BigQuery

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

Large scale data warehouse service with append-only tables

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Document store
Key-value store

Relational DBMS

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

Score	0.02
Rank	#374	Overall
	#52	Document stores
	#38	Graph DBMS
	#56	Key-value stores
	#38	Time Series DBMS

Score	9.16
Rank	#43	Overall
	#27	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Website

arcadedb.com

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.dbase.com

cloud.google.com/bigquery

Technical documentation

docs.arcadedb.com

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

Developer

Arcade Data

Atos Convergence Creators

Asthon Tate

Google

Initial release

2021

2016

1979

2010

Current release

September 2021

1703

dBASE 2019, 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

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

All OS with a Java VM

Linux

DOS

dBase Classic
Windows

dBase Pro

hosted

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

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

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

LDAP

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

Supported programming languages

Java

All languages with LDAP bindings

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

not for dBase internal data, but IDE does support transactions when accessing external DBMS

Since BigQuery is designed for querying data

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

LDAP bind authentication

Access rights for users and roles

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.