DBMS > Drizzle vs. Galaxybase vs. Google BigQuery vs. ToroDB

System Properties Comparison Drizzle vs. Galaxybase vs. Google BigQuery vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Scalable, ACID-compliant native distributed parallel graph platform

Large scale data warehouse service with append-only tables

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

galaxybase.com

cloud.google.com/bigquery

github.com/torodb/server

Technical documentation

cloud.google.com/bigquery/docs

Developer

Drizzle project, originally started by Brian Aker

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Google

8Kdata

Initial release

2008

2017

2010

2016

Current release

7.2.4, September 2012

Nov 20, November 2021

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

AGPL-V3

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 Java

Java

Server operating systems

FreeBSD
Linux
OS X

Linux

hosted

All OS with a Java 7 VM

Data scheme

yes

Strong typed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

with proprietary extensions

yes

APIs and other access methods

JDBC

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

Go
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined procedures and functions

user defined functions

in JavaScript

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role-based access control

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

Google Cloud Identity & Access Management (IAM)

Access rights for 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.