DBMS > AlaSQL vs. Dgraph vs. Google Cloud Datastore vs. MySQL vs. Tkrzw

System Properties Comparison AlaSQL vs. Dgraph vs. Google Cloud Datastore vs. MySQL vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Distributed and scalable native Graph DBMS

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

Widely used open source RDBMS

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Relational DBMS

Graph DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

alasql.org

dgraph.io

cloud.google.com/datastore

www.mysql.com

dbmx.net/tkrzw

Technical documentation

github.com/AlaSQL/alasql

dgraph.io/docs

cloud.google.com/datastore/docs

dev.mysql.com/doc

Developer

Andrey Gershun & Mathias R. Wulff

Dgraph Labs, Inc.

Google

Oracle

since 2010, originally MySQL AB, then Sun

Mikio Hirabayashi

Initial release

2014

2016

2008

1995

2020

Current release

8.4.0, April 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

JavaScript

C and C++

C++

Server operating systems

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

Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

JavaScript API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

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

.Net
Go
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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

yes

proprietary syntax

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication via Raft

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

none

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

none

Immediate Consistency

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

yes

only for local storage and DOM-storage

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

using specific database classes

User concepts

Access control

Planned for future releases

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

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.