DBMS > Quasardb vs. RocksDB vs. Sqrrl vs. Titan

System Properties Comparison Quasardb vs. RocksDB vs. Sqrrl vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Distributed, high-performance timeseries database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Adaptable, secure NoSQL built on Apache Accumulo

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Time Series DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

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

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

quasar.ai

rocksdb.org

sqrrl.com

github.com/thinkaurelius/titan

Technical documentation

doc.quasar.ai/master

github.com/facebook/rocksdb/wiki

github.com/thinkaurelius/titan/wiki

Developer

quasardb

Facebook, Inc.

Amazon

originally Sqrrl Data, Inc.

Aurelius, owned by DataStax

Initial release

2009

2013

2012

Current release

3.14.1, January 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

BSD

commercial

Open Source

Apache license, version 2.0

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

C++

Java

Server operating systems

BSD
Linux
OS X
Windows

Linux

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

HTTP API

C++ API
Java API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C
C++
Go
Java
Perl
Python
Ruby

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

horizontal partitioning

Sharding

making use of Hadoop

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with selectable replication factor

yes

selectable replication factor

making use of Hadoop

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

ACID

yes

Atomic updates per row, document, or graph entity

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

User authentification and security via Rexster Graph Server

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.