DBMS > Drizzle vs. Google Cloud Datastore vs. Microsoft Azure Data Explorer vs. Microsoft SQL Server vs. WakandaDB

System Properties Comparison Drizzle vs. Google Cloud Datastore vs. Microsoft Azure Data Explorer vs. Microsoft SQL Server vs. WakandaDB

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.

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

Fully managed big data interactive analytics platform

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

column oriented

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store
Graph DBMS
Spatial DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

cloud.google.com/datastore

azure.microsoft.com/services/data-explorer

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

wakanda.github.io

Technical documentation

cloud.google.com/datastore/docs

docs.microsoft.com/en-us/azure/data-explorer

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

wakanda.github.io/doc

Developer

Drizzle project, originally started by Brian Aker

Google

Microsoft

Wakanda SAS

Initial release

2008

2019

1989

2012

Current release

7.2.4, September 2012

cloud service with continuous releases

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

C++, JavaScript

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (GQL)

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

JDBC

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

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

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

RESTful HTTP API

Supported programming languages

C
C++
Java
PHP

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

JavaScript

Server-side scripts

Stored procedures

using Google App Engine

Yes, possible languages: KQL, Python, R

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

yes

Triggers

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

Multi-source replication using Paxos

yes

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

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

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.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

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

Azure Active Directory Authentication

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.