DBMS > Dragonfly vs. Google BigQuery vs. Infobright vs. Quasardb

System Properties Comparison Dragonfly vs. Google BigQuery vs. Infobright vs. Quasardb

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

Large scale data warehouse service with append-only tables

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Distributed, high-performance timeseries database

Primary database model

Key-value store

Relational DBMS

Time Series DBMS

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

Score	0.44
Rank	#255	Overall
	#38	Key-value stores

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	0.13
Rank	#332	Overall
	#28	Time Series DBMS

Website

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

cloud.google.com/bigquery

ignitetech.com/softwarelibrary/infobrightdb

quasar.ai

Technical documentation

www.dragonflydb.io/docs

cloud.google.com/bigquery/docs

doc.quasar.ai/master

Developer

DragonflyDB team and community contributors

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

quasardb

Initial release

2023

2010

2005

2009

Current release

1.0, March 2023

3.14.1, January 2024

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

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

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++

Server operating systems

Linux

hosted

Linux
Windows

BSD
Linux
OS X
Windows

Data scheme

scheme-free

yes

schema-free

Typing

predefined data types such as float or date

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

yes

integer and binary

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

Knowledge Grid Technology used instead

yes

with tags

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

HTTP 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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

Triggers

publish/subscribe channels provide some trigger functionality

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of command blocks and scripts

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

by using LevelDB

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

Password-based authentication

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Cryptographically strong user authentication and audit trail

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.