DBMS > Atos Standard Common Repository vs. Ehcache vs. Geode vs. KairosDB

System Properties Comparison Atos Standard Common Repository vs. Ehcache vs. Geode vs. KairosDB

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

A widely adopted Java cache with tiered storage options

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

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

Document store
Key-value store

Key-value store

Time Series DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Website

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

www.ehcache.org

geode.apache.org

github.com/kairosdb/kairosdb

Technical documentation

www.ehcache.org/documentation

geode.apache.org/docs

kairosdb.github.io

Developer

Atos Convergence Creators

Terracotta Inc, owned by Software AG

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

Initial release

2016

2009

2002

2013

Current release

1703

3.10.0, March 2022

1.1, February 2017

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.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

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

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)

APIs and other access methods

LDAP

JCache

Java Client API
Memcached protocol
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

All languages with LDAP bindings

Java

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

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication

selectable replication factor

based on Cassandra

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

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes

supports JTA and can work as an XA resource

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

simple password-based access control

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

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

provided by Google News

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

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

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

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

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

provided by Google News

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

Expo: Real Time A/B Testing and Monitoring with Spark Streaming and Kafka at Walmart Labs
24 May 2019, InfoQ.com

provided by Google News

Share this page