DBMS > Atos Standard Common Repository vs. GeoMesa vs. HugeGraph vs. LevelDB vs. ToroDB

System Properties Comparison Atos Standard Common Repository vs. GeoMesa vs. HugeGraph vs. LevelDB vs. ToroDB

Editorial information provided by DB-Engines

Name

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

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

A fast-speed and highly-scalable Graph DBMS

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Key-value store

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Website

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

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

github.com/google/leveldb

github.com/torodb/server

Technical documentation

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

hugegraph.apache.org/docs

github.com/google/leveldb/blob/main/doc/index.md

Developer

Atos Convergence Creators

CCRi and others

Baidu

Google

8Kdata

Initial release

2016

2014

2018

2011

2016

Current release

1703

5.0.0, May 2024

0.9

1.23, February 2021

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

BSD

Open Source

AGPL-V3

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

Java

C++

Java

Server operating systems

Linux

Linux
macOS
Unix

Illumos
Linux
OS X
Windows

All OS with a Java 7 VM

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

string, integer, double, boolean, date, object_id

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

also supports composite index and range index

SQL

Support of SQL

APIs and other access methods

LDAP

Java API
RESTful HTTP API
TinkerPop Gremlin

Supported programming languages

All languages with LDAP bindings

Groovy
Java
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

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

with automatic compression on writes

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

yes

depending on the DBMS used for storage

Users, roles and permissions

Access rights for 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Critical Apache HugeGraph Flaw Let Attackers Execute Remote Code
23 April 2024, GBHackers

provided by Google News

Pliops unveils XDP-Rocks for RocksDB – Blocks and Files
19 October 2022, Blocks & Files

Microsoft Teams stores auth tokens as cleartext in Windows, Linux, Macs
14 September 2022, BleepingComputer

XanMod, Liquorix Kernels Offer Some Advantages On AMD Ryzen 5 Notebook
26 July 2021, Phoronix

Threat Thursday: BlackGuard Infostealer Rises from Russian Underground Markets
21 April 2022, BlackBerry Blog

Rust-Based Info Stealers Abuse GitHub Codespaces
19 May 2023, Trend Micro

provided by Google News

Share this page