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

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

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Large scale data warehouse service with append-only tables

Primary database model

Key-value store

Relational 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.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

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

www.exasol.com

www.gbase.cn

cloud.google.com/bigquery

Technical documentation

www.dragonflydb.io/docs

www.exasol.com/resources

cloud.google.com/bigquery/docs

Developer

DragonflyDB team and community contributors

Exasol

General Data Technology Co., Ltd.

Google

Initial release

2023

2000

2004

2010

Current release

1.0, March 2023

GBase 8a, GBase 8s, GBase 8c

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

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

Server operating systems

Linux

hosted

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

yes

Standard with numerous extensions

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

.Net
JDBC
ODBC
WebSocket

ADO.NET
C API
JDBC
ODBC

RESTful HTTP/JSON API

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

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

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

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

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

Password-based authentication

Access rights for users, groups and roles according to SQL-standard

yes

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

Google Cloud Identity & Access Management (IAM)

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.