DBMS > Atos Standard Common Repository vs. Geode vs. Transbase vs. YottaDB

System Properties Comparison Atos Standard Common Repository vs. Geode vs. Transbase vs. YottaDB

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

A resource-optimized, high-performance, universally applicable RDBMS

A fast and solid embedded Key-value store

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

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

geode.apache.org

www.transaction.de/en/products/transbase.html

yottadb.com

Technical documentation

geode.apache.org/docs

www.transaction.de/en/products/transbase/features.html

yottadb.com/resources/documentation

Developer

Atos Convergence Creators

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

Transaction Software GmbH

YottaDB, LLC

Initial release

2016

2002

1987

2001

Current release

1703

1.1, February 2017

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free development license

Open Source

AGPL 3.0

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

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
macOS
Solaris
Windows

Docker
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

SQL-like query language (OQL)

yes

by using the Octo plugin

APIs and other access methods

LDAP

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

All languages with LDAP bindings

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

yes

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

yes

Transaction concepts

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

Atomic execution of specific operations

yes, on a single node

yes

optimistic locking

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

Access rights per client and object definable

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

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

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

provided by Google News

Share this page