Skip to main content

Planning for Cloud Computing Failures

Last week's outage for some of Amazon's cloud computing customers has highlighted the importance of planning for cloud failures. While the large data centers run by the most competent companies such as Amazon, Google, and Microsoft have enviable performance and reliability, they are not perfect. Customers of cloud computing must still reckon with backups, failover, and contingency plans if they want to ensure a high level of availability.

I predict that we will witness a significant number of cloud computing failures which will affect large and small companies, governments, and individuals. Some will be from fumbles by the major players, but an even larger number will come from new companies and dabblers in cloud computing. The whitehot hype around cloud computing will create large numbers of businesses that ultimately fail.

Cloud computing is creating a smaller echo of the dot com boom, with small companies armed with ambitious business plans trying to carve out their pieces of the cloud pie. The frontier mentality will lead to aggressive marketing, aggressive sales, and aggressive pricing.

What will happen when new cloud companies start to run out of capital, or their venture capital masters give them a tighter leash? Will their priority be to help customers find a safe landing? How many cloud providers are willing to give customers backups that could quickly be restored with another provider?

The implication for customers of cloud computing is that customers must maintain options for moving from one provider to another or even moving systems in-house if necessary to protect themselves from technical and business contingencies.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan