DBMS > GridGain vs. Prometheus vs. Riak TS vs. XTDB

System Properties Comparison GridGain vs. Prometheus vs. Riak TS vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

Open-source Time Series DBMS and monitoring system

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Document store

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.gridgain.com

prometheus.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.gridgain.com/docs/index.html

prometheus.io/docs

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

www.xtdb.com/docs

Developer

GridGain Systems, Inc.

Open Source, formerly Basho Technologies

Juxt Ltd.

Initial release

2007

2015

2019

Current release

GridGain 8.5.1

3.0.0, September 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

MIT License

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++, .Net

Erlang

Clojure

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes, extensible-data-notation format

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

Import of XML data possible

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes, limited

limited SQL, making use of Apache Calcite

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

HTTP REST
JDBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

Clojure
Java

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

Erlang

Triggers

yes (cache interceptors and events)

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

by Federation

selectable replication factor

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Security Hooks for custom implementations

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

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks and Files

GridGain's 2023 Growth Positions Company for Strong 2024
24 January 2024, PR Newswire

GridGain Unified Real-Time Data Platform Version 8.9 Addresses Today's More Complex Real-Time Data Processing ...
12 October 2023, GlobeNewswire

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain: Product Overview and Analysis
5 June 2019, eWeek

provided by Google News

VTEX scales to 150 million metrics using Amazon Managed Service for Prometheus | Amazon Web Services
10 March 2024, AWS Blog

Exadata Real-Time Insight - Quick Start
3 April 2024, Oracle

OpenTelemetry vs. Prometheus: You can’t fix what you can’t see
29 March 2024, IBM

VictoriaMetrics Offers Prometheus Replacement for Time Series Monitoring
17 July 2023, The New Stack

Linux System Monitoring with Prometheus, Grafana, and collectd
1 February 2024, Linux Journal

provided by Google News

Share this page