DBMS > Derby vs. MySQL vs. PouchDB vs. Snowflake vs. Transbase

System Properties Comparison Derby vs. MySQL vs. PouchDB vs. Snowflake vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Widely used open source RDBMS

JavaScript DBMS with an API inspired by CouchDB

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

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

Technical documentation

db.apache.org/derby/manuals/index.html

dev.mysql.com/doc

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

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

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

1997

1995

2012

2014

1987

Current release

10.17.1.0, November 2023

8.4.0, April 2024

7.1.1, June 2019

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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

Implementation language

Java

C and C++

JavaScript

C and C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

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

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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

via views

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

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

JavaScript

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

View functions in JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

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

by using IndexedDB, WebSQL or LevelDB as backend

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.