DBMS > chDB vs. Drizzle vs. Google Cloud Datastore vs. Microsoft Azure Table Storage

System Properties Comparison chDB vs. Drizzle vs. Google Cloud Datastore vs. Microsoft Azure Table Storage

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

An embedded SQL OLAP Engine powered by ClickHouse

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

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

Primary database model

Relational DBMS

Document store

Wide column store

Secondary database models

Time Series DBMS

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

Score	0.07
Rank	#376	Overall
	#158	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Website

github.com/chdb-io/chdb

cloud.google.com/datastore

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

Technical documentation

doc.chdb.io

cloud.google.com/datastore/docs

Developer

Drizzle project, originally started by Brian Aker

Google

Microsoft

Initial release

2023

2008

2012

Current release

7.2.4, September 2012

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Server operating systems

server-less

FreeBSD
Linux
OS X

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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.

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

with proprietary extensions

SQL-like query language (GQL)

APIs and other access methods

JDBC

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

RESTful HTTP API

Supported programming languages

Bun
C
C++
Go
JavaScript (Node.js)
Python
Rust

C
C++
Java
PHP

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

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

Server-side scripts

Stored procedures

using Google App Engine

Triggers

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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.

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

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

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

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.

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)

Access rights based on private key authentication or shared access signatures

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

Best cloud storage of 2024
4 June 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Working with Azure to Use and Manage Data Lakes
7 March 2024, Simplilearn

How to use Azure Table storage in .Net
14 January 2019, InfoWorld

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

Inside Azure File Storage
7 October 2015, azure.microsoft.com

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

provided by Google News

Share this page