DBMS > Blueflood vs. Graph Engine vs. RocksDB vs. Sphinx

System Properties Comparison Blueflood vs. Graph Engine vs. RocksDB vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Time Series DBMS

Graph DBMS
Key-value store

Key-value store

Search engine

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

www.graphengine.io/docs/manual

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Rackspace

Microsoft

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2013

2010

2013

2001

Current release

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MIT License

Open Source

BSD

Open Source

GPL version 2, commercial licence available

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

.NET and C

C++

Server operating systems

Linux
OS X

.NET

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

predefined scheme

yes

schema-free

yes

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

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (SphinxQL)

APIs and other access methods

HTTP REST

RESTful HTTP API

C++ API
Java API

Proprietary protocol

Supported programming languages

C#
C++
F#
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

User concepts

Access control

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.