DBMS > GBase vs. IBM Db2 vs. Memcached vs. MySQL

System Properties Comparison GBase vs. IBM Db2 vs. Memcached vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Common in IBM host environments, 2 different versions for host and Windows/Linux

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Document store
Spatial DBMS

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.gbase.cn

www.ibm.com/products/db2

www.memcached.org

www.mysql.com

Technical documentation

www.ibm.com/docs/en/db2

github.com/memcached/memcached/wiki

dev.mysql.com/doc

Developer

General Data Technology Co., Ltd.

IBM

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2004

1983

host version

2003

1995

Current release

GBase 8a, GBase 8s, GBase 8c

12.1, October 2016

1.6.27, May 2024

8.4.0, April 2024

License

Commercial or Open Source

commercial

free version is available

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

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

Implementation language

C, Java, Python

C and C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

SQL

Support of SQL

Standard with numerous extensions

yes

with proprietary extensions

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
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

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

only with Windows/Unix/Linux Version

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

none

Repcached, a Memcached patch, provides this functionallity

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

yes

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

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.