Store migrasjoner, ny database, nytt rammeverk, ny plattform, er høy risiko fordi de rører ved alt og leverer ingen bruksersyn verdi før de er ferdige. Den sikre tilnærmingen er inkrementell og reversibel, aldri en stor omlegging. Du migrerer i skiver du kan validere og rulle tilbake.
En sikker migrasjonsplaybok
1. Know WHY — a migration with no clear payoff isn't worth the risk.
2. Migrate INCREMENTALLY — never flip everything at once.
3. Run OLD and NEW in parallel — strangler-fig pattern.
4. Use feature flags / DUAL WRITES to shift traffic gradually.
5. VERIFY continuously — compare old vs. new outputs (shadow traffic).
6. Keep a ROLLBACK path at every step.
7. Clean up the old system only AFTER the new one is proven.
