DBMS > MySQL vs. openGauss vs. searchxml vs. Vitess

System Properties Comparison MySQL vs. openGauss vs. searchxml vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

An enterprise-class RDBMS compatible with high-performance, high-availability and high-performance originally developed by Huawei

DBMS for structured and unstructured content wrapped with an application server

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.08
Rank	#183	Overall
	#84	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.mysql.com

gitee.com/opengauss
opengauss.org

www.searchxml.net/category/products

vitess.io

Technical documentation

dev.mysql.com/doc

docs.opengauss.org/en
gitee.com/opengauss/docs

www.searchxml.net/support/handouts

vitess.io/docs

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Huawei and openGauss community

informationpartners gmbh

The Linux Foundation, PlanetScale

Initial release

1995

2019

2015

2013

Current release

8.4.0, April 2024

3.0, March 2022

1.0

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

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.

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

Implementation language

C and C++

C, C++, Java

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Windows

Docker
Linux
macOS

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

yes

with proprietary extensions

ANSI SQL 2011

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C
C++
Java

C++

most other programming languages supported via APIs

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

yes

proprietary syntax

yes

on the application server

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by range, list and hash)

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

sychronisation to multiple collections

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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

ACID

multiple readers, single writer

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

Domain, group and role-based access control at the document level and for application services

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.