DBMS > Geode vs. Infobright vs. Riak KV

System Properties Comparison Geode vs. Infobright vs. Riak KV

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Distributed, fault tolerant key-value store

Primary database model

Key-value store

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

geode.apache.org

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

geode.apache.org/docs

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

Developer

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

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenSource, formerly Basho Technologies

Initial release

2002

2005

2009

Current release

1.1, February 2017

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache version 2, commercial enterprise edition

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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

Linux
OS X

Data scheme

schema-free

yes

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

Knowledge Grid Technology used instead

restricted

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

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

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

yes, on a single node

ACID

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

yes, using Riak Security

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, O'Reilly Media

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

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

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

provided by Google News

Share this page