DBMS > Atos Standard Common Repository vs. Google Cloud Spanner vs. SQLite vs. TigerGraph vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Spanner vs. SQLite vs. TigerGraph vs. Yaacomo

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Widely used embeddable, in-process RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS

Relational DBMS

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

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

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

cloud.google.com/spanner

www.sqlite.org

www.tigergraph.com

yaacomo.com

Technical documentation

cloud.google.com/spanner/docs

www.sqlite.org/docs.html

docs.tigergraph.com

Developer

Atos Convergence Creators

Google

Dwayne Richard Hipp

Q2WEB GmbH

Initial release

2016

2017

2000

2017

2009

Current release

1703

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Public Domain

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

Server operating systems

Linux

hosted

server-less

Linux

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

dynamic column types

yes

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

Query statements complying to ANSI 2011

yes

SQL-92 is not fully supported

SQL-like query language (GSQL)

yes

APIs and other access methods

LDAP

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication with 3 replicas for regional instances.

none

Source-replica replication

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

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Strict serializable isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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)

Role-based access control

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.