DBMS > Graph Engine vs. Riak TS vs. Rockset vs. SQLite

System Properties Comparison Graph Engine vs. Riak TS vs. Rockset vs. SQLite

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

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

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Time Series DBMS

Document store

Relational DBMS

Secondary database models

Relational DBMS
Search engine

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

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

rockset.com

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

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

docs.rockset.com

www.sqlite.org/docs.html

Developer

Microsoft

Open Source, formerly Basho Technologies

Rockset

Dwayne Richard Hipp

Initial release

2010

2015

2019

2000

Current release

3.0.0, September 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

commercial

Open Source

Public Domain

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

C++

Server operating systems

.NET

Linux
OS X

hosted

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

dynamic typing

yes

not rigid because of 'dynamic typing' concept.

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

restricted

all fields are automatically indexed

yes

SQL

Support of SQL

yes, limited

Read-only SQL queries, including JOINs

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.