DBMS > Infobright vs. PostGIS vs. Prometheus vs. Riak KV vs. SpaceTime

System Properties Comparison Infobright vs. PostGIS vs. Prometheus vs. Riak KV vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of PostgreSQL

Open-source Time Series DBMS and monitoring system

Distributed, fault tolerant key-value store

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

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

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

postgis.net

prometheus.io

www.mireo.com/spacetime

Technical documentation

postgis.net/documentation

prometheus.io/docs

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

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenSource, formerly Basho Technologies

Mireo

Initial release

2005

2015

2009

2020

Current release

3.4.2, February 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

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

Open Source

GPL v2.0

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

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

Erlang

C++

Server operating systems

Linux
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

Knowledge Grid Technology used instead

yes

restricted

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

RESTful HTTP API

Supported programming languages

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

.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

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

Sharding

no "single point of failure"

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

based on PostgreSQL

yes

by Federation

selectable replication factor

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets 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

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

yes

based on PostgreSQL

yes, using Riak Security

yes

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the 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

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

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

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

provided by Google News

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

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

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

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

provided by Google News

Share this page