Databases 10 min read

MySQL High Availability vs Oracle High Availability: Can MySQL Replace Oracle in the Financial Industry?

The livestream discusses MySQL's high‑availability architectures compared with Oracle's, analyzes share‑nothing versus share‑everything designs, logical versus physical logging, and concludes that MySQL's share‑nothing and logical binlog replication are better suited for modern financial‑industry workloads, while also covering audience Q&A and upcoming topics.

Aikesheng Open Source Community
Aikesheng Open Source Community
Aikesheng Open Source Community
MySQL High Availability vs Oracle High Availability: Can MySQL Replace Oracle in the Financial Industry?

The program "MySQL冲冲冲" is a livestream series jointly organized by the IMG community and the iKexing open‑source community, focusing on MySQL technical topics; the third episode aired on the 17th and its transcript is presented here.

Topic: MySQL High Availability vs Oracle High Availability – can MySQL replace Oracle’s monopoly in the financial sector?

1. Architecture comparison

MySQL offers two HA solutions: traditional master‑slave replication (including semi‑sync in 5.5 and lossless semi‑sync in 5.7) and Group Replication (MGR) based on the Paxos consensus algorithm, which supports multi‑write nodes and follows a share‑nothing model.

Oracle’s HA relies on Data Guard (similar to MySQL replication) and Real Application Clusters (RAC), which follows a share‑everything model because all nodes write to a shared storage, creating a single point of failure.

The speaker argues that share‑nothing architectures like MySQL’s MGR are more future‑proof, while RAC’s shared storage can become a bottleneck.

2. Log mechanisms

MySQL uses logical binary logs (binlog) for replication, whereas Oracle uses physical redo logs that record page‑level changes, giving Oracle faster sync for large DDL but causing MySQL replication lag for short transactions.

MySQL 5.7 introduced parallel replication and MySQL 8.0 added fast‑add‑column to reduce DDL lag; logical logs also enable flexible integration with big‑data platforms (e.g., CDC, syncing to ClickHouse).

3. Can MySQL replace Oracle in finance?

The speaker states that the question is not binary; MySQL is already gaining market share in banks, with thousands of instances deployed, and the trend suggests a gradual replacement, especially for non‑core workloads.

Q&A Highlights

MySQL is unlikely to become a paid product; the open‑source community can sustain development.

Domestic database service providers have good prospects, especially after cloud adoption.

Oracle DBAs can transition to MySQL by learning similar concepts and distributed design.

MGR synchronizes via GTID‑based logs; a deeper dive will be covered in a future episode.

Bank DBAs enjoy high salaries; career growth depends on skill and market demand.

Upcoming episode preview

Topic: "Can MySQL Group Replication be used at large scale in production?" plus community giveaways and links to the live stream on Bilibili (room 22230895) every Thursday 20:30‑21:30, hosted by teacher Jiang Chengyao.

High Availabilitydatabase architectureMySQLOracleFinancial IndustryGroup ReplicationLogical Logging
Aikesheng Open Source Community
Written by

Aikesheng Open Source Community

The Aikesheng Open Source Community provides stable, enterprise‑grade MySQL open‑source tools and services, releases a premium open‑source component each year (1024), and continuously operates and maintains them.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.