DBMS > GigaSpaces vs. PostGIS vs. Riak KV

System Properties Comparison GigaSpaces vs. PostGIS vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

Primary database model

Document store
Object oriented DBMS

Values are user defined objects

Spatial DBMS

Key-value store

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

Secondary database models

Graph DBMS
Search engine

Relational DBMS

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

Score	1.02
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

www.gigaspaces.com

postgis.net

Technical documentation

docs.gigaspaces.com/latest/landing.html

postgis.net/documentation

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

Developer

Gigaspaces Technologies

OpenSource, formerly Basho Technologies

Initial release

2000

2005

2009

Current release

15.5, September 2020

3.4.2, February 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial licenses available

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

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

Server operating systems

Linux
macOS
Solaris
Windows

Linux
OS X

Data scheme

schema-free

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.

XML can be used for describing objects metadata

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-99 for query and DML statements

yes

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C++
Java
Python
Scala

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, event driven architecture

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

based on PostgreSQL

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

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

Role-based access control

yes

based on PostgreSQL

yes, using Riak Security

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

GigaSpaces to hand out almost $14 million in dividends following Cloudify’s acquisition by Dell
19 July 2023, CTech

Data Sciences Corporation partners with GigaSpaces Technologies to usher DIH technology to enterprises in SA
10 October 2023, ITWeb

GigaSpaces Announces Version 16.0 with Breakthrough Data Integration Tools to Ease Enterprises' Digital ...
3 November 2021, PR Newswire

GigaSpaces Spins Off Cloudify, Its Open Source Cloud Orchestration Unit
27 July 2017, Data Center Knowledge

Your occasional storage digest with GigaSpaces, Virtana and NAND ship data – Blocks and Files
7 December 2020, Blocks & Files

provided by Google News

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

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

Basho Revamps Riak Open-Source Database
17 September 2014, InformationWeek

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

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

Share this page