DBMS > AlaSQL vs. Drizzle vs. Google Cloud Bigtable vs. WakandaDB

System Properties Comparison AlaSQL vs. Drizzle vs. Google Cloud Bigtable vs. WakandaDB

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

JavaScript DBMS library

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

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store
Wide column store

Object oriented DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

alasql.org

cloud.google.com/bigtable

wakanda.github.io

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigtable/docs

wakanda.github.io/doc

Developer

Andrey Gershun & Mathias R. Wulff

Drizzle project, originally started by Brian Aker

Google

Wakanda SAS

Initial release

2014

2008

2015

2012

Current release

7.2.4, September 2012

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GNU GPL

commercial

Open Source

AGPLv3, extended commercial license 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

JavaScript

C++

C++, JavaScript

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
OS X

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC

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

RESTful HTTP API

Supported programming languages

JavaScript

C
C++
Java
PHP

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

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

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

yes

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

Google introduces Cloud Bigtable managed NoSQL database to process data at scale
6 May 2015, VentureBeat

provided by Google News

Share this page