DBMS > Graph Engine vs. PostGIS vs. Riak KV vs. STSdb vs. TempoIQ

System Properties Comparison Graph Engine vs. PostGIS vs. Riak KV vs. STSdb vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Graph DBMS
Key-value store

Spatial DBMS

Key-value store

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

Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.graphengine.io

postgis.net

github.com/STSSoft/STSdb4

tempoiq.com (offline)

Technical documentation

www.graphengine.io/docs/manual

postgis.net/documentation

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

Developer

Microsoft

OpenSource, formerly Basho Technologies

STS Soft SC

TempoIQ

Initial release

2010

2005

2009

2011

2012

Current release

3.4.2, February 2024

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

.NET and C

Erlang

Server operating systems

.NET

Linux
OS X

Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

.NET Client API

HTTP API

Supported programming languages

C#
C++
F#
Visual Basic

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#
Java

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

yes

based on PostgreSQL

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

yes

based on PostgreSQL

yes, using Riak Security

simple authentication-based access control

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

Trinity
2 June 2023, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

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

Basho distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page