DBMS > Geode vs. Heroic vs. Riak TS vs. SWC-DB

System Properties Comparison Geode vs. Heroic vs. Riak TS vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A high performance, scalable Wide Column DBMS

Primary database model

Key-value store

Time Series DBMS

Wide column store

Secondary database models

Time Series DBMS

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

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

geode.apache.org

github.com/spotify/heroic

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

geode.apache.org/docs

spotify.github.io/heroic

www.tiot.jp/riak-docs/riak/ts/latest

Developer

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

Spotify

Open Source, formerly Basho Technologies

Alex Kashirin

Initial release

2002

2014

2015

2020

Current release

1.1, February 2017

3.0.0, September 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

GPL V3

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

Erlang

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

via Elasticsearch

restricted

SQL

Support of SQL

SQL-like query language (OQL)

yes, limited

SQL-like query language

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API
Native Erlang Interface

Proprietary protocol
Thrift

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

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

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

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

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

Enterprise NoSQL Database for the IoT Becomes Open Source
11 May 2016, ENGINEERING.com

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page