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

System Properties Comparison Atos Standard Common Repository vs. Geode vs. LevelDB 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

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

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

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

Primary database model

Document store
Key-value store

Key-value store

Document store

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

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

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

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

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

geode.apache.org

github.com/google/leveldb

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

Technical documentation

geode.apache.org/docs

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

www.xtdb.com/docs

Developer

Atos Convergence Creators

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

Google

Juxt Ltd.

Initial release

2016

2002

2011

2019

Current release

1703

1.1, February 2017

1.23, February 2021

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD

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

Clojure

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Illumos
Linux
OS X
Windows

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

Data scheme

Schema and schema-less with LDAP views

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

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST
JDBC

Supported programming languages

All languages with LDAP bindings

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Clojure
Java

Server-side scripts

Stored procedures

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

none

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

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

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

LevelDB in Ruby — SitePoint
22 October 2014, SitePoint

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

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

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

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

provided by Google News

Share this page