DBMS > Atos Standard Common Repository vs. Dgraph vs. GeoMesa vs. Ignite vs. RocksDB

System Properties Comparison Atos Standard Common Repository vs. Dgraph vs. GeoMesa vs. Ignite vs. RocksDB

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

Distributed and scalable native Graph DBMS

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Key-value store

Graph DBMS

Spatial DBMS

Key-value store
Relational DBMS

Key-value store

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

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

Technical documentation

dgraph.io/docs

www.geomesa.org/documentation/stable/user/index.html

apacheignite.readme.io/docs

github.com/facebook/rocksdb/wiki

Developer

Atos Convergence Creators

Dgraph Labs, Inc.

CCRi and others

Apache Software Foundation

Facebook, Inc.

Initial release

2016

2014

2015

2013

Current release

1703

4.0.5, February 2024

Apache Ignite 2.6

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Scala

C++, Java, .Net

C++

Server operating systems

Linux

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

LDAP

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

depending on storage layer

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

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

depending on storage layer

yes

User concepts

Access control

LDAP bind authentication

Planned for future releases

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

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.