DBMS > Atos Standard Common Repository vs. Google Cloud Datastore vs. IBM Cloudant vs. Microsoft SQL Server

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Datastore vs. IBM Cloudant vs. Microsoft SQL Server

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Database as a Service offering based on Apache CouchDB

Microsofts flagship relational DBMS

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

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

cloud.google.com/datastore

www.ibm.com/products/cloudant

www.microsoft.com/en-us/sql-server

Technical documentation

cloud.google.com/datastore/docs

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/en-US/sql/sql-server

Developer

Atos Convergence Creators

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Initial release

2016

2008

2010

1989

Current release

1703

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

restricted free version is 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

Erlang

C++

Server operating systems

Linux

hosted

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

LDAP

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

All languages with LDAP bindings

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

using Google App Engine

View functions (Map-Reduce) in JavaScript

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.