DBMS > Atos Standard Common Repository vs. CouchDB vs. Google BigQuery vs. Rockset

System Properties Comparison Atos Standard Common Repository vs. CouchDB vs. Google BigQuery vs. Rockset

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

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Document store
Key-value store

Document store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

using the Geocouch extension

Relational DBMS
Search engine

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

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

couchdb.apache.org

cloud.google.com/bigquery

rockset.com

Technical documentation

docs.couchdb.org/en/stable

cloud.google.com/bigquery/docs

docs.rockset.com

Developer

Atos Convergence Creators

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

Rockset

Initial release

2016

2005

2010

2019

Current release

1703

3.3.3, December 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Erlang

C++

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

via views

all fields are automatically indexed

SQL

Support of SQL

yes

Read-only SQL queries, including JOINs

APIs and other access methods

LDAP

RESTful HTTP/JSON API

HTTP REST

Supported programming languages

All languages with LDAP bindings

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

improved architecture with release 2.0

none

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

atomic operations within a single document possible

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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 can be defined per database

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.