DBMS > Dragonfly vs. GBase vs. Google BigQuery vs. JanusGraph

System Properties Comparison Dragonfly vs. GBase vs. Google BigQuery vs. JanusGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Large scale data warehouse service with append-only tables

A Graph DBMS optimized for distributed clusters

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

Primary database model

Key-value store

Relational DBMS

Graph DBMS

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

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

www.gbase.cn

cloud.google.com/bigquery

janusgraph.org

Technical documentation

www.dragonflydb.io/docs

cloud.google.com/bigquery/docs

docs.janusgraph.org

Developer

DragonflyDB team and community contributors

General Data Technology Co., Ltd.

Google

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2023

2004

2010

2017

Current release

1.0, March 2023

GBase 8a, GBase 8s, GBase 8c

0.6.3, February 2023

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

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.

Implementation language

C++

C, Java, Python

Java

Server operating systems

Linux

hosted

Linux
OS X
Unix
Windows

Data scheme

scheme-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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

Standard with numerous extensions

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
C API
JDBC
ODBC

RESTful HTTP/JSON API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Clojure
Java
Python

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

none

yes

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

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

User concepts

Access control

Password-based authentication

yes

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.