DBMS > Atos Standard Common Repository vs. CockroachDB vs. EJDB vs. Google BigQuery vs. Kinetica

System Properties Comparison Atos Standard Common Repository vs. CockroachDB vs. EJDB vs. Google BigQuery vs. Kinetica

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Large scale data warehouse service with append-only tables

Fully vectorized database across both GPUs and CPUs

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Website

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

www.cockroachlabs.com

github.com/Softmotions/ejdb

cloud.google.com/bigquery

www.kinetica.com

Technical documentation

www.cockroachlabs.com/docs

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigquery/docs

docs.kinetica.com

Developer

Atos Convergence Creators

Cockroach Labs

Softmotions

Google

Kinetica

Initial release

2016

2015

2012

2010

2012

Current release

1703

24.1.0, May 2024

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

GPLv2

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

Server operating systems

Linux

Linux
macOS
Windows

server-less

hosted

Linux

Data scheme

Schema and schema-less with LDAP views

dynamic schema

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

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

yes, wire compatible with PostgreSQL

yes

SQL-like DML and DDL statements

APIs and other access methods

LDAP

JDBC

in-process shared library

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Read/Write 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

GPU vRAM or System RAM

User concepts

Access control

LDAP bind authentication

Role-based access control

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles on table level

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.