1. Coexistence Patterns advanced

    A migration will take eighteen months, during which old and new systems both serve production. How should the coexistence period be designed?

    2 min answer digitcoexistenceroutingconsistency
  2. Coexistence Patterns advanced

    During a multi-year migration, old and new systems must coexist. Which coexistence patterns are sustainable and which accumulate debt?

    2 min answer coexistencedual-writeownershipreconciliation
  3. Coexistence Patterns advanced

    Eighteen months into a coexistence period, customer records are authoritative in the new system and order records are still authoritative in the old one. A refund credits the customer and cancels the order line. What happens the first time the credit commits and the cancellation is rejected?

    3 min answer coexistencewrite ownershipsagascompensation
  4. Coexistence Patterns advanced

    Old and new stores both hold 42 million customer records during a coexistence period. The nightly full-row comparison now takes 6 hours 40 minutes against a 4-hour window, and the legacy side serves the export at about 1800 rows per second. Roughly what does a hash-bucket comparison cost instead, and which assumption decides whether it fits?

    3 min answer coexistence-patternsreconciliationmerklehashing
  5. Coexistence Patterns advanced

    Your cutover plan says switch reads, then switch writes, then decommission. A reviewer asks what happens at 02:00 if the new store turns out to be wrong after writes have moved. What mechanism makes the write switch reversible, and what is the honest unavailability window?

    3 min answer youtubevitesscutoverreverse-replication