DBMS > Hyprcubd vs. JanusGraph vs. LevelDB vs. MySQL vs. QuestDB

System Properties Comparison Hyprcubd vs. JanusGraph vs. LevelDB vs. MySQL vs. QuestDB

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Serverless Time Series DBMS

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used open source RDBMS

A high performance open source SQL database for time series data

Primary database model

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Website

hyprcubd.com (offline)

janusgraph.org

github.com/google/leveldb

www.mysql.com

questdb.io

Technical documentation

docs.janusgraph.org

github.com/google/leveldb/blob/main/doc/index.md

dev.mysql.com/doc

questdb.io/docs

Developer

Hyprcubd, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Google

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

Initial release

2017

2011

1995

2014

Current release

0.6.3, February 2023

1.23, February 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++

C and C++

Java (Zero-GC), C++, Rust

Server operating systems

hosted

Linux
OS X
Unix
Windows

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

SQL with time-series extensions

APIs and other access methods

gRPC (https)

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

Clojure
Java
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID for single-table writes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

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

yes

with automatic compression on writes

yes

In-memory capabilities

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

yes

through memory mapped files

User concepts

Access control

token access

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

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.