DBMS > 4D vs. Atos Standard Common Repository vs. Coveo vs. Google BigQuery vs. Rockset

System Properties Comparison 4D vs. Atos Standard Common Repository vs. Coveo vs. Google BigQuery vs. Rockset

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Large scale data warehouse service with append-only tables

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS

Document store
Key-value store

Search engine

Relational DBMS

Document store

Secondary database models

Relational DBMS
Search engine

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

www.4d.com

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

www.coveo.com

cloud.google.com/bigquery

rockset.com

Technical documentation

developer.4d.com

docs.coveo.com

cloud.google.com/bigquery/docs

docs.rockset.com

Developer

4D, Inc

Atos Convergence Creators

Coveo

Google

Rockset

Initial release

1984

2016

2012

2010

2019

Current release

v20, April 2023

1703

License

Commercial or Open Source

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++

Server operating systems

OS X
Windows

Linux

hosted

Data scheme

yes

Schema and schema-less with LDAP views

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

close to SQL 92

yes

Read-only SQL queries, including JOINs

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

RESTful HTTP API

RESTful HTTP/JSON API

HTTP REST

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

C#
Java
JavaScript
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

yes

none

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

yes

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

Users and groups

LDAP bind authentication

granular access controls, API key management, content filters

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and organizations can be defined via Rockset console

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.