DBMS > GeoMesa vs. RDF4J vs. Riak TS vs. Rockset

System Properties Comparison GeoMesa vs. RDF4J vs. Riak TS vs. Rockset

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Secondary database models

Relational DBMS
Search engine

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

www.geomesa.org

rdf4j.org

rockset.com

Technical documentation

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

rdf4j.org/documentation

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

docs.rockset.com

Developer

CCRi and others

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Open Source, formerly Basho Technologies

Rockset

Initial release

2014

2004

2015

2019

Current release

5.0.1, July 2024

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

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

Scala

Java

Erlang

C++

Server operating systems

Linux
OS X
Unix
Windows

Linux
OS X

hosted

Data scheme

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

restricted

all fields are automatically indexed

SQL

Support of SQL

yes, limited

Read-only SQL queries, including JOINs

APIs and other access methods

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP API
Native Erlang Interface

HTTP REST

Supported programming languages

Java
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

Go
Java
JavaScript (Node.js)
Python

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

depending on storage layer

none

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

yes

depending on the DBMS used for storage

Access rights for users and organizations can be defined via Rockset console

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

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

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

provided by Google News

OpenAI’s first acquisition is an enterprise data startup
21 June 2024, The Verge

OpenAI Looks To Boost Data Retrieval Capabilities Of Its GenAI Technology With Rockset Acquisition
26 June 2024, CRN

OpenAI acquires Rockset to enhance ChatGPT real-time data processing
25 June 2024, InfoWorld

An Analysis Of OpenAI’s Acquisition Of Rockset And Its Strategic Significance
24 June 2024, Forbes

OpenAI Buys Enterprise Startup to Help Customers Sift Through Data
21 June 2024, Bloomberg

provided by Google News

Share this page