> pitfalls that could introduce corruption or loss of data sometimes, repairing broken data is easier than, say, upgrading a god damn hot DB. MVCC is overrate

> pitfalls that could introduce corruption or loss of data sometimes, repairing broken data is easier than, say, upgrading a god damn hot DB. MVCC is overrated. Not every row in a busy MySQL table is your transactional wallet balance. But to upgrade a DB you have to deal with every field every row every table, and data keeps changing, which is a real headache Fixing a range of broken data, however, can be done by a junior developer. If you rely on rdbms for a single source of truth you are probably fucked anyway. btw I do hate DDL changes in MySQL.