Design an Enterprise Architecture Strategy
The enterprise architecture (EA) team is constantly challenged to articulate the value of its function.
The CIO has asked the Enterprise Architecture team to help him understand the value the team brings to his department.
While there may be an IT strategy documented, no EA strategy exists, or at best, some loose collection of ideas form the basis of the EA strategy.
The business focuses on a projects, ignoring holistic value of an overarching architecture.
This “project-only” view results in poor technology investments, resulting in massive technical debt, and most enterprises are not ready to adjust to the Agile practices, further increasing technical debt.
In addition, enterprises struggle with rapidly changing technologies.
Keep your systems dormant until disaster strikes. Prepare as much of your environment as possible without tapping into compute resources. Enjoy the low at-rest costs, and leverage the reliability of the cloud in your failover.
Avoid failure on the failback! Bringing up your systems in the cloud is a great temporary solution, but an expensive long-term strategy. Make sure you have a plan to get back on premises.
Leverage cloud DR as a start for cloud migration. Cloud DR provides a gateway for broader infrastructure lift and shift to cloud IaaS, but this should only be the first phase of a longer-term roadmap that ends in multi-service hybrid cloud.
Impact and Result
Calculate the cost of your DR solution with a cloud vendor. Test your systems often to build out more accurate budgets and to define failover and failback action plans to increase confidence in your capabilities.
Define “good enough” performance by consulting with the business and setting correct expectations for the recovery state.
Dig deeper into the various flavors of cloud-based DR beyond backup and restore, including pilot light, warm standby, and multi-site recovery. Each of these has unique benefits and challenges when done in the cloud.