DBMS > Geode vs. IRONdb vs. Splunk vs. Tkrzw

System Properties Comparison Geode vs. IRONdb vs. Splunk vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Analytics Platform for Big Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

geode.apache.org

www.circonus.com/solutions/time-series-database/

www.splunk.com

dbmx.net/tkrzw

Technical documentation

geode.apache.org/docs

docs.circonus.com/irondb/category/getting-started

docs.splunk.com/Documentation/Splunk

Developer

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

Circonus LLC.

Splunk Inc.

Mikio Hirabayashi

Initial release

2002

2017

2003

2020

Current release

1.1, February 2017

V0.10.20, January 2018

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 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

C and C++

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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)

SQL-like query language (Circonus Analytics Query Language: CAQL)

Splunk Search Processing Language for search commands

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API

HTTP REST

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes, in Lua

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

configurable replication factor, datacenter aware

Multi-source replication

none

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 per node, eventual consistency across nodes

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

using specific database classes

User concepts

Access control

Access rights per client and object definable

Access rights for users and roles

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

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

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

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

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

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

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

provided by Google News

Share this page