DBMS > Dgraph vs. Dragonfly vs. Google BigQuery vs. Google Cloud Bigtable vs. Tarantool

System Properties Comparison Dgraph vs. Dragonfly vs. Google BigQuery vs. Google Cloud Bigtable vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Graph DBMS

Key-value store

Relational DBMS

Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

dgraph.io

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

cloud.google.com/bigquery

cloud.google.com/bigtable

www.tarantool.io

Technical documentation

dgraph.io/docs

www.dragonflydb.io/docs

cloud.google.com/bigquery/docs

cloud.google.com/bigtable/docs

www.tarantool.io/en/doc

Developer

Dgraph Labs, Inc.

DragonflyDB team and community contributors

Google

Initial release

2016

2023

2010

2015

2008

Current release

1.0, March 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSL 1.1

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Server operating systems

Linux
OS X
Windows

Linux

hosted

BSD
Linux
macOS

Data scheme

schema-free

scheme-free

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

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

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Open binary protocol

Supported programming languages

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

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++
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

Lua, C and SQL stored procedures

Triggers

publish/subscribe channels provide some trigger functionality

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

Since BigQuery is designed for querying data

Atomic single-row operations

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Planned for future releases

Password-based authentication

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

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.