3 ms·
This has been recognized for a long time. Those change-over things are really severe. Really severe problems. - Joseph Henry Condon, Bell Labs ... via https://
by contingencies 4y ago
This has been recognized for a long time.
Those change-over things are really severe. Really severe problems. - Joseph Henry Condon, Bell Labs ... via https://github.com/globalcitizen/taoup https://github.com/globalcitizen/taoup
However, we have much better tools now, such as end to end / black box testing with mature client automation stacks, high availability clustering, CI/CD, distributed architectures, middleware proxies, protocol-level support for temporary failures and retries, mature caching systems and fault tolerant hardware and software infrastructure. So it's practically not as hard as it once was, because if you've got your ducks in a row you can use a battle-proven method and/or get fallbacks for free.
- gonzo41 4y agoYes but all of that is a good idea to implement on a new project starting today with lots of money and a big competent team. Migrations are hard when you have to fight with the project management triangle and then realize that the migration you're doing is on a system which is old, bespoke or not supported. Or all of the above. I like your optimism, but it's always hard work. The most important part of all processes is knowing when you're past a point at which you cannot turn back from.