DBMS > Bangdb vs. Google Cloud Datastore vs. Microsoft Azure Table Storage vs. MySQL

System Properties Comparison Bangdb vs. Google Cloud Datastore vs. Microsoft Azure Table Storage vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used open source RDBMS

Primary database model

Document store
Graph DBMS
Time Series DBMS

Document store

Wide column store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.07
Rank	#346	Overall
	#47	Document stores
	#35	Graph DBMS
	#32	Time Series DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

bangdb.com

cloud.google.com/datastore

azure.microsoft.com/en-us/services/storage/tables

www.mysql.com

Technical documentation

docs.bangdb.com

cloud.google.com/datastore/docs

dev.mysql.com/doc

Developer

Sachin Sinha, BangDB

Google

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2008

2012

1995

Current release

BangDB 2.0, October 2021

9.0.0, July 2024

License

Commercial or Open Source

Open Source

BSD 3

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

yes, details here

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

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

Proprietary protocol
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Java
Python

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

using Google App Engine

yes

proprietary syntax

Triggers

yes, Notifications (with Streaming only)

Callbacks using the Google Apps Engine

yes

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

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication using Paxos

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

optimistic locking

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

table locks or row locks depending on storage engine

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

yes

User concepts

Access control

yes (enterprise version only)

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

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or 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.