Big Bang Rewrite vs Strangler Pattern
Developers might consider a Big Bang Rewrite when a legacy system is so outdated, poorly documented, or tightly coupled that incremental changes are impractical or too costly, such as with obsolete technology stacks or monolithic architectures that hinder innovation meets developers should use the strangler pattern when dealing with monolithic legacy systems that are difficult to maintain or scale, but where a complete rewrite is too risky or disruptive. Here's our take.
Big Bang Rewrite
Developers might consider a Big Bang Rewrite when a legacy system is so outdated, poorly documented, or tightly coupled that incremental changes are impractical or too costly, such as with obsolete technology stacks or monolithic architectures that hinder innovation
Big Bang Rewrite
Nice PickDevelopers might consider a Big Bang Rewrite when a legacy system is so outdated, poorly documented, or tightly coupled that incremental changes are impractical or too costly, such as with obsolete technology stacks or monolithic architectures that hinder innovation
Pros
- +It can be justified for critical business systems requiring a complete overhaul to meet modern requirements, like scalability or security, but carries high risks of failure, budget overruns, and disruption to operations
- +Related to: legacy-system-migration, strangler-pattern
Cons
- -Specific tradeoffs depend on your use case
Strangler Pattern
Developers should use the Strangler Pattern when dealing with monolithic legacy systems that are difficult to maintain or scale, but where a complete rewrite is too risky or disruptive
Pros
- +It is particularly useful in scenarios requiring modernization of enterprise applications, such as migrating from on-premises to cloud-based architectures or updating outdated technology stacks, as it allows for incremental changes without downtime
- +Related to: microservices, legacy-system-migration
Cons
- -Specific tradeoffs depend on your use case
The Verdict
Use Big Bang Rewrite if: You want it can be justified for critical business systems requiring a complete overhaul to meet modern requirements, like scalability or security, but carries high risks of failure, budget overruns, and disruption to operations and can live with specific tradeoffs depend on your use case.
Use Strangler Pattern if: You prioritize it is particularly useful in scenarios requiring modernization of enterprise applications, such as migrating from on-premises to cloud-based architectures or updating outdated technology stacks, as it allows for incremental changes without downtime over what Big Bang Rewrite offers.
Developers might consider a Big Bang Rewrite when a legacy system is so outdated, poorly documented, or tightly coupled that incremental changes are impractical or too costly, such as with obsolete technology stacks or monolithic architectures that hinder innovation
Disagree with our pick? nice@nicepick.dev