> Think about components you rely on for your service. How long would it take you to stand up or migrate to an alternative. Architect at a F500 here. It would

> Think about components you rely on for your service. How long would it take you to stand up or migrate to an alternative. Architect at a F500 here. It would take us easily 2 years to roll out a solution, get migrated to it, and have it implemented, tested, and signed off. Probably another year (or more) to work out all of the kinks or handle the stuff that wasn't in the initial build (e.g. phase 2 expansions, etc.). There is a reason we do 5 year TCOs, and it's not just cuz of the depreciation schedules. Also the reason we lean to things with 5-, or 10-year maintenance cycles. 1-year notice is not enough, full-stop. Not talking about rolling our own solution here either, this is COTS being deployed in a 99.999% environment in multiple countries.