DBMS > Amazon Neptune vs. GeoMesa vs. gStore vs. Riak TS

System Properties Comparison Amazon Neptune vs. GeoMesa vs. gStore vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A native Graph DBMS to store and maintain very large RDF datasets.

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

Primary database model

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

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

aws.amazon.com/neptune

www.geomesa.org

en.gstore.cn

Technical documentation

aws.amazon.com/neptune/developer-resources

www.geomesa.org/documentation/stable/user/index.html

en.gstore.cn/#/enDocs

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

Developer

Amazon

CCRi and others

Open Source, formerly Basho Technologies

Initial release

2017

2014

2016

2015

Current release

5.0.0, May 2024

1.2, November 2023

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

BSD

Open Source

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

Scala

C++

Erlang

Server operating systems

hosted

Linux

Linux
OS X

Data scheme

schema-free

yes

schema-free and OWL/RDFS-schema support

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

yes, limited

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

HTTP API
SPARQL 1.1

HTTP API
Native Erlang Interface

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
PHP
Python

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

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

depending on storage layer

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

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

links between datasets can be stored

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

In-memory capabilities

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

depending on storage layer

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

yes

depending on the DBMS used for storage

Users, roles and permissions, Role-Based Access Control (RBAC) supported

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

AWS Weekly Roundup: LlamaIndex support for Amazon Neptune, force AWS CloudFormation stack deletion, and more ...
27 May 2024, AWS Blog

Amazon Neptune Analytics is now available in the AWS Europe (London) Region
14 March 2024, AWS Blog

Amazon Neptune Analytics is now generally available
29 November 2023, AWS Blog

Analyze large amounts of graph data to get insights and find trends with Amazon Neptune Analytics | Amazon Web ...
29 November 2023, AWS Blog

Amazon Neptune announces support for data APIs in the AWS SDK
22 February 2024, AWS Blog

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

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

provided by Google News

Share this page