DBMS > Bangdb vs. Drizzle vs. EsgynDB vs. Google BigQuery

System Properties Comparison Bangdb vs. Drizzle vs. EsgynDB vs. Google BigQuery

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.

Description

Converged and high performance database for device data, events, time series, document and graph

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Large scale data warehouse service with append-only tables

Primary database model

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

bangdb.com

www.esgyn.cn

cloud.google.com/bigquery

Technical documentation

docs.bangdb.com

cloud.google.com/bigquery/docs

Developer

Sachin Sinha, BangDB

Drizzle project, originally started by Brian Aker

Esgyn

Google

Initial release

2012

2008

2015

2010

Current release

BangDB 2.0, October 2021

7.2.4, September 2012

License

Commercial or Open Source

Open Source

BSD 3

Open Source

GNU GPL

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

C++

C++, Java

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux

hosted

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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.

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

yes

with proprietary extensions

yes

APIs and other access methods

Proprietary protocol
RESTful HTTP API

JDBC

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Java
Python

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

Triggers

yes, Notifications (with Streaming only)

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Foreign keys

Referential integrity

yes

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, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes, run db with in-memory only mode

User concepts

Access control

yes (enterprise version only)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.