> We don't write migrations for our C++, so why the heck are we writing migrations for our DBs? In-memory data structures are ephemeral. You "migrate" by resta

> We don't write migrations for our C++, so why the heck are we writing migrations for our DBs? In-memory data structures are ephemeral. You "migrate" by restarting or replacing code entirely. If you have an on-disk format that basically acts as a memory snapshot, someone writes a migration script, which is usually not recognised as such. Databases seem weird and icky and mismatched, but it's because of the D in ACID. Durable data has momentum, more force is required to change its vector than the mist that lives in memory.