DBMS > Drizzle vs. OrigoDB vs. PlanetScale vs. Transbase

System Properties Comparison Drizzle vs. OrigoDB vs. PlanetScale vs. Transbase

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.

A fully ACID in-memory object graph database

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

origodb.com

planetscale.com

www.transaction.de/en/products/transbase.html

Technical documentation

origodb.com/docs

planetscale.com/docs

www.transaction.de/en/products/transbase/features.html

Developer

Drizzle project, originally started by Brian Aker

Robert Friberg et al

PlanetScale

Transaction Software GmbH

Initial release

2008

2009

under the name LiveDB

2020

1987

Current release

7.2.4, September 2012

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

commercial

free development license

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

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

Docker
Linux
macOS

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Java
PHP

.Net

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

yes

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

Write ahead log

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 authorization

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Named to Fortune 2023 Best Small Workplaces
31 August 2023, Business Wire

How to Migrate to PlanetScale's Serverless Database
14 October 2021, The New Stack

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

Share this page