1. Rebuild vs Re-architect advanced

    A 15-year-old system is unmaintainable. The team wants a full rewrite. What do you advise?

    2 min answer modernizationriskdecision
  2. Rebuild vs Re-architect advanced

    A platform's core system cannot support a capability the business needs. The team proposes a rebuild. What must be true for rebuild to beat incremental re-architecture?

    2 min answer rebuildrewriteincrementalrisk
  3. Rebuild vs Re-architect advanced

    An organisation running Kafka at trillions of messages per day concludes the coordination and rebalancing model no longer fits and builds a replacement. What evidence should exist before replacing a proven system rather than tuning it?

    3 min answer linkedinkafkanorthguardreplacement
  4. Rebuild vs Re-architect intermediate

    Review this plan. Eighteen months to rebuild the policy engine. Feature parity is required before any traffic moves. The legacy team is frozen to bug fixes only so that no effort is wasted on code that will be thrown away. What would you remove, what would you change, and what would you leave alone?

    3 min answer rewritefeature-parityarchitecture-reviewincremental-migration
  5. Rebuild vs Re-architect advanced

    YouTube's database team was running a growing fleet of MySQL instances with sharding logic spread through application code. Rather than replace MySQL or rewrite the application, they built Vitess as a routing tier between the two, open-sourcing it in 2011; it graduated in the CNCF in 2019. What did that choice buy, what did it cost, and where would copying it be a mistake?

    3 min answer youtubevitessshardingproxy layer