DBMS > Drizzle vs. Galaxybase vs. gStore vs. ToroDB vs. Vitess

System Properties Comparison Drizzle vs. Galaxybase vs. gStore vs. ToroDB vs. Vitess

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.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Scalable, ACID-compliant native distributed parallel graph platform

A native Graph DBMS to store and maintain very large RDF datasets.

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	0.04
Rank	#359	Overall
	#37	Graph DBMS
	#18	RDF stores

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

galaxybase.com

en.gstore.cn

github.com/torodb/server

vitess.io

Technical documentation

en.gstore.cn/#/enDocs

vitess.io/docs

Developer

Drizzle project, originally started by Brian Aker

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

8Kdata

The Linux Foundation, PlanetScale

Initial release

2008

2017

2016

2013

Current release

7.2.4, September 2012

Nov 20, November 2021

1.2, November 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

BSD

Open Source

AGPL-V3

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C and Java

C++

Java

Server operating systems

FreeBSD
Linux
OS X

Linux

All OS with a Java 7 VM

Docker
Linux
macOS

Data scheme

yes

Strong typed schema

schema-free and OWL/RDFS-schema support

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JDBC

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

HTTP API
SPARQL 1.1

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C++
Java
PHP

Go
Java
Python

C++
Java
JavaScript (Node.js)
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined procedures and functions

yes

proprietary syntax

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Role-based access control

Users, roles and permissions, Role-Based Access Control (RBAC) supported

Access rights for users and roles

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.

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

做国产图数据库，「创邻科技」将拓展国际市场| 新科技创业-36氪
5 April 2023, 36kr

创邻科技，位居IDC MarketScape中国图数据库市场领导者类别原创
13 September 2023, blog.csdn.net

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page