To explore the responsibilities of the architect deploying to the cloud for DR and availability in better detail, let’s introduce a notional “customer” with one of the simplest application scenarios. There are many more complicated scenarios that are every-day experience for many of us, but as with many of our strategic roles, start with (and
Modern cloud offerings (especially from well-established providers) should offer at least 3 levels of availability strategy: Capabilities “built into” the pricing for base system function. Capabilities available at a single geography for availability management. Multi-geography strategic capabilities for robust availability management. [This post is the second of 3 parts. Part 1 addresses the business context
Any architect in the industry has seen their business – or one of their customers – sold on introducing a “cloud” service as the cure-call for what ails business IT. It’s almost a magic hand-wave to watch with the sales and marketing teams: outage times? Wave your hand and it’s no longer important. Multi-data-center deployment?