The document discusses different go-live scenarios for replacing an existing system with new infrastructure. It describes the "big bang" approach where the existing system is switched off and the new system goes live immediately, which is risky as there is no rollback option. It also outlines the "parallel changeover" scenario where both systems run simultaneously for weeks to test the new system extensively before switching off the old system, allowing easier rollback and minimizing risk but increasing costs.
The document discusses different go-live scenarios for replacing an existing system with new infrastructure. It describes the "big bang" approach where the existing system is switched off and the new system goes live immediately, which is risky as there is no rollback option. It also outlines the "parallel changeover" scenario where both systems run simultaneously for weeks to test the new system extensively before switching off the old system, allowing easier rollback and minimizing risk but increasing costs.
The document discusses different go-live scenarios for replacing an existing system with new infrastructure. It describes the "big bang" approach where the existing system is switched off and the new system goes live immediately, which is risky as there is no rollback option. It also outlines the "parallel changeover" scenario where both systems run simultaneously for weeks to test the new system extensively before switching off the old system, allowing easier rollback and minimizing risk but increasing costs.
Mam Rabia saleem Go live scenarios • Go live scenarios • There are a number of scenarios that can be used to put the new infrastructure in • production as the replacement for an existing system – to “Go Live”: • · Big Bang – In the big bang scenario, at a set time, the existing system • is switched off and the new system is immediately put in production, • possibly after a short data migration run. This is the riskiest scenario • because it may be impossible to roll back to the old system after the • system is live for some time, and because downtime can occur when • something goes wrong during the switchover • Parallel changeover – In this scenario, both the new and the existing • system run simultaneously for some time (typically weeks). This allows • for testing the new system on both functionality and non-functional • attributes, and ensuring it works with live production data before switching • off the existing system. As both systems are running and processing data, • switching back is possible at any time, minimizing risk. A big • disadvantage of this scenario is the cost of maintaining both systems and • the possible extra work to keep both systems in sync. Also, many system • designs don’t allow running two systems in parallel, for instance, if the • system has many data interfaces with other systems.