DBMS > Drizzle vs. Firebase Realtime Database vs. Microsoft SQL Server vs. WakandaDB

System Properties Comparison Drizzle vs. Firebase Realtime Database vs. Microsoft SQL Server 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

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Microsofts flagship relational DBMS

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

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

www.microsoft.com/en-us/sql-server

wakanda.github.io

Technical documentation

firebase.google.com/docs/database

learn.microsoft.com/en-US/sql/sql-server

wakanda.github.io/doc

Developer

Drizzle project, originally started by Brian Aker

Google

acquired by Google 2014

Microsoft

Wakanda SAS

Initial release

2008

2012

1989

2012

Current release

7.2.4, September 2012

SQL Server 2022, November 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

GNU GPL

commercial

restricted free version is available

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

C++

C++, JavaScript

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux
Windows

Linux
OS X
Windows

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP API

Supported programming languages

C
C++
Java
PHP

Java
JavaScript
Objective-C

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

JavaScript

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

hooks for callbacks inside the server can be used.

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

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

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

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.