DBMS > Atos Standard Common Repository vs. Google BigQuery vs. Kingbase vs. Newts vs. Vitess

System Properties Comparison Atos Standard Common Repository vs. Google BigQuery vs. Kingbase vs. Newts vs. Vitess

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

Large scale data warehouse service with append-only tables

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Time Series DBMS based on Cassandra

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

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

cloud.google.com/bigquery

www.kingbase.com.cn

opennms.github.io/newts

vitess.io

Technical documentation

cloud.google.com/bigquery/docs

github.com/OpenNMS/newts/wiki

vitess.io/docs

Developer

Atos Convergence Creators

Google

BeiJing KINGBASE Information technologies inc.

OpenNMS Group

The Linux Foundation, PlanetScale

Initial release

2016

2010

1999

2014

2013

Current release

1703

V8.0, August 2021

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0, commercial licenses available

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 and Java

Java

Server operating systems

Linux

hosted

Linux
Windows

Linux
OS X
Windows

Docker
Linux
macOS

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

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

yes

Standard with numerous extensions

yes

with proprietary extensions

APIs and other access methods

LDAP

RESTful HTTP/JSON API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

HTTP REST
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Multi-source replication
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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

Since BigQuery is designed for querying data

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.