DBMS > Graph Engine vs. PostGIS vs. Postgres-XL vs. Riak TS

System Properties Comparison Graph Engine vs. PostGIS vs. Postgres-XL vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Graph DBMS
Key-value store

Spatial DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

Document store
Spatial 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	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.graphengine.io

postgis.net

www.postgres-xl.org

Technical documentation

www.graphengine.io/docs/manual

postgis.net/documentation

www.postgres-xl.org/documentation

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

Developer

Microsoft

Open Source, formerly Basho Technologies

Initial release

2010

2005

2014

since 2012, originally named StormDB

2015

Current release

3.4.2, February 2024

10 R1, October 2018

3.0.0, September 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL v2.0

Open Source

Mozilla public license

Open Source

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

.NET and C

Erlang

Server operating systems

.NET

Linux
macOS

Linux
OS X

Data scheme

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

distributed, parallel query execution

yes, limited

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Native Erlang Interface

Supported programming languages

C#
C++
F#
Visual Basic

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
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

yes

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

yes

based on PostgreSQL

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

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 datasets can be stored

Transaction concepts

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

ACID

MVCC

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

fine grained access rights according to SQL-standard

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

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page