DBMS > Dragonfly vs. GBase vs. Google BigQuery vs. Teradata Aster

System Properties Comparison Dragonfly vs. GBase vs. Google BigQuery vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

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

Platform for big data analytics on multistructured data sources and types

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.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.gbase.cn

cloud.google.com/bigquery

Technical documentation

www.dragonflydb.io/docs

cloud.google.com/bigquery/docs

Developer

DragonflyDB team and community contributors

General Data Technology Co., Ltd.

Google

Teradata

Initial release

2023

2004

2010

2005

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

Linux

Data scheme

scheme-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

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

ADO.NET
JDBC
ODBC
OLE DB

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

R packages

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

ACID

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

yes

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

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.