DBMS > Atos Standard Common Repository vs. EventStoreDB vs. SAP HANA vs. TigerGraph

System Properties Comparison Atos Standard Common Repository vs. EventStoreDB vs. SAP HANA vs. TigerGraph

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

Industrial-strength, open-source database solution built from the ground up for event sourcing.

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Document store
Key-value store

Event Store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

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

www.eventstore.com

www.sap.com/products/hana.html

www.tigergraph.com

Technical documentation

developers.eventstore.com

help.sap.com/hana

docs.tigergraph.com

Developer

Atos Convergence Creators

Event Store Limited

SAP

Initial release

2016

2012

2010

2017

Current release

1703

21.2, February 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

Linux
Windows

Appliance or cloud-service

Linux

Data scheme

Schema and schema-less with LDAP views

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

SQL-like query language (GSQL)

APIs and other access methods

LDAP

JDBC
ODBC

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

Supported programming languages

All languages with LDAP bindings

C++
Java

Server-side scripts

Stored procedures

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Relationships in graphs

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

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

yes

Role-based access control

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.