DBMS > 4D vs. Atos Standard Common Repository vs. Google BigQuery vs. HugeGraph vs. SQream DB

System Properties Comparison 4D vs. Atos Standard Common Repository vs. Google BigQuery vs. HugeGraph vs. SQream DB

Editorial information provided by DB-Engines

Name

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

Description

Application development environment with integrated database management system

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

Large scale data warehouse service with append-only tables

A fast-speed and highly-scalable Graph DBMS

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Graph DBMS

Relational DBMS

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

Score	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.15
Rank	#339	Overall
	#33	Graph DBMS

Score	0.73
Rank	#228	Overall
	#105	Relational DBMS

Website

www.4d.com

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

cloud.google.com/bigquery

github.com/hugegraph
hugegraph.apache.org

sqream.com

Technical documentation

developer.4d.com

cloud.google.com/bigquery/docs

hugegraph.apache.org/docs

docs.sqream.com

Developer

4D, Inc

Atos Convergence Creators

Google

Baidu

SQream Technologies

Initial release

1984

2016

2010

2018

2017

Current release

v20, April 2023

1703

0.9

2022.1.6, December 2022

License

Commercial or Open Source

commercial

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

OS X
Windows

Linux

hosted

Linux
macOS
Unix

Linux

Data scheme

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

yes

yes, ANSI Standard SQL Types

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

also supports composite index and range index

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

RESTful HTTP/JSON API

Java API
RESTful HTTP API
TinkerPop Gremlin

.Net
JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Groovy
Java
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

asynchronous Gremlin script jobs

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

none

yes

depending on used storage backend, e.g. Cassandra and HBase

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

depending on used storage backend, e.g. Cassandra and HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

ACID

Atomic execution of specific operations

Since BigQuery is designed for querying data

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.

yes

User concepts

Access control

Users and groups

LDAP bind authentication

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

Google Cloud Identity & Access Management (IAM)

Users, roles and permissions

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.