MOmountainview·Aug 11, 2025Submission
Online Schema Change Tool for MySQL 8.0
1 points · Open discussionblock
spirit
Go2025–2025
block / spirit
spirit
Online schema change and data operations for MySQL 8.0+
2Distinct people
2Mentions
0Explicit recommenders
204GitHub stars
What to know before exploring
What it is
Online schema change and data operations for MySQL 8.0+
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week2 dated mentions
Observed mentions: 2025-05-23 19:54:26 UTC to 2025-08-11 02:07:37 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| May 19 | 2025-05-19 00:00:00 UTC | 2025-05-26 00:00:00 UTC | 1 | 0 | 1 |
| May 26 | 2025-05-26 00:00:00 UTC | 2025-06-02 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2 | 2025-06-02 00:00:00 UTC | 2025-06-09 00:00:00 UTC | 0 | 0 | 0 |
| Jun 9 | 2025-06-09 00:00:00 UTC | 2025-06-16 00:00:00 UTC | 0 | 0 | 0 |
| Jun 16 | 2025-06-16 00:00:00 UTC | 2025-06-23 00:00:00 UTC | 0 | 0 | 0 |
| Jun 23 | 2025-06-23 00:00:00 UTC | 2025-06-30 00:00:00 UTC | 0 | 0 | 0 |
| Jun 30 | 2025-06-30 00:00:00 UTC | 2025-07-07 00:00:00 UTC | 0 | 0 | 0 |
| Jul 7 | 2025-07-07 00:00:00 UTC | 2025-07-14 00:00:00 UTC | 0 | 0 | 0 |
| Jul 14 | 2025-07-14 00:00:00 UTC | 2025-07-21 00:00:00 UTC | 0 | 0 | 0 |
| Jul 21 | 2025-07-21 00:00:00 UTC | 2025-07-28 00:00:00 UTC | 0 | 0 | 0 |
| Jul 28 | 2025-07-28 00:00:00 UTC | 2025-08-04 00:00:00 UTC | 0 | 0 | 0 |
| Aug 4 | 2025-08-04 00:00:00 UTC | 2025-08-11 00:00:00 UTC | 0 | 0 | 0 |
| Aug 11 | 2025-08-11 00:00:00 UTC | 2025-08-18 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sources> The only feature that Aurora (MySQL) has that is remotely impressive
Aurora is one of the only options if you need low-lag physical replication in a MySQL-compatible environment. That makes it operationally feasible to execute large/heavy writes or DDL which would normally cause too much replication lag on traditional (async binlog-based) MySQL replicas.
Granted, there's some important fine print: long transactions will still block InnoDB purge of old row versions, and in Aurora that's cluster-wide. But in any case, personally I'd consider nearly-lag-free replication to be an important differentiator. This can be leveraged in interesting ways, for example CashApp's `spirit` OSC tool (https://github.com/block/spirit) can do online schema changes blazing-fast because it doesn't need to throttle its write rate to avoid replication lag.
Sca
Read the rest
le-to-zero is also nice for dev/test environments.
That said, I do agree with your overall point that Aurora was majorly over-marketed. And Amazon's capture of so much revenue in the MySQL space has been extremely detrimental for the MySQL ecosystem, especially considering Aurora's modifications are proprietary/closed-source.