DBMS > Atos Standard Common Repository vs. Geode vs. Hawkular Metrics vs. KairosDB

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

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

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

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	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Website

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

geode.apache.org

www.hawkular.org

github.com/kairosdb/kairosdb

Technical documentation

geode.apache.org/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

kairosdb.github.io

Developer

Atos Convergence Creators

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

Community supported by Red Hat

Initial release

2016

2002

2014

2013

Current release

1703

1.1, February 2017

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

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

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

All languages with LDAP bindings

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

Go
Java
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on Cassandra

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

selectable replication factor

based on Cassandra

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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, on a single node

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

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

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

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

RDBMS and Apache Geode Data Movement: Low Latency ETL Pipeline by Using Cloud-Native Event Driven ...
30 June 2018, InfoQ.com

provided by Google News

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

The re-emergence of time-series – O'Reilly
6 April 2013, oreilly.com

provided by Google News

Share this page