Remix.run Logo
pvtmert 9 hours ago

The main difference being the time it takes to recover/reverse the decision.

Second point is: You don't need to reverse the decision you took, instead you may find a way to fix the impact but not the root-cause.

It's like when one fucks up the MySQL replication and the data consistency is corrupted. One can manually (and slowly) fix the inconsistency with downtime. Or, spin up a whole new cluster from an existing well-known node/state. Some entities may be missing, but you could gradually add them back later.

Not a reversible, but recoverable decision.

Amazon goes by with one-way vs two-way door decisions internally. Sometimes adding much bureaucracy to the equation. Just-do-it/Bias-for-action aspect usually don't go as far as the recovery period prolongs.