DBMS > Atos Standard Common Repository vs. Galaxybase vs. Geode vs. XTDB

System Properties Comparison Atos Standard Common Repository vs. Galaxybase vs. Geode vs. XTDB

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

Scalable, ACID-compliant native distributed parallel graph platform

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Key-value store

Graph DBMS

Key-value store

Document store

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

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

galaxybase.com

geode.apache.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

geode.apache.org/docs

www.xtdb.com/docs

Developer

Atos Convergence Creators

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Juxt Ltd.

Initial release

2016

2017

2002

2019

Current release

1703

Nov 20, November 2021

1.1, February 2017

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

MIT License

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

C and Java

Java

Clojure

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java 8 (and higher) VM
Linux

Data scheme

Schema and schema-less with LDAP views

Strong typed schema

schema-free

Typing

predefined data types such as float or date

optional

yes

yes, extensible-data-notation format

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 (OQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

LDAP

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST
JDBC

Supported programming languages

All languages with LDAP bindings

Go
Java
Python

.Net
All JVM based languages
C++
Groovy
Java
Scala

Clojure
Java

Server-side scripts

Stored procedures

user defined procedures and functions

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual 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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Role-based access control

Access rights per client and object definable

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

Recent citations in the news

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

provided by Google News

做国产图数据库，「创邻科技」将拓展国际市场| 新科技创业
5 April 2023, 36kr

创邻科技，位居IDC MarketScape中国图数据库市场领导者类别
13 September 2023, CSDN

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page