DBMS > Atos Standard Common Repository vs. Google Cloud Datastore vs. Microsoft SQL Server vs. SwayDB vs. Tarantool

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Datastore vs. Microsoft SQL Server vs. SwayDB vs. Tarantool

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

Microsofts flagship relational DBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Key-value store

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

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

cloud.google.com/datastore

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

swaydb.simer.au

www.tarantool.io

Technical documentation

cloud.google.com/datastore/docs

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

www.tarantool.io/en/doc

Developer

Atos Convergence Creators

Google

Microsoft

Simer Plaha

Initial release

2016

2008

1989

2018

2008

Current release

1703

SQL Server 2022, November 2022

2.10.0, May 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GNU Affero GPL V3.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Scala

C and C++

Server operating systems

Linux

hosted

Linux
Windows

BSD
Linux
macOS

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

optional

yes, details here

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

LDAP

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

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

Open binary protocol

Supported programming languages

All languages with LDAP bindings

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

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

Java
Kotlin
Scala

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

using Google App Engine

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

Lua, C and SQL stored procedures

Triggers

yes

Callbacks using the Google Apps Engine

yes

yes, before/after data modification events, on replication events, client session events

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

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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.

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID

Atomic execution of operations

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

LDAP bind authentication

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.