This article might be a good example of why software as a service (SaaS) should not be called “cloud.” Equating a subscription software delivery model to cloud masks its true value.
Let’s start with the old analogy of comparing cloud computing to an electrical utility. NetSuite is adamant that building and maintaining its own power plants is important, when what customers really value is their software.
Also, the author of the article appears to be saying that Infor requires that its clients use Amazon Web Services (AWS).
If this is so, it’s amazing that these two “cloud” companies have got it so wrong.
The author raises questions about how “SaaSy” Infor’s applications really are for multi-tenant, security, and automation. The real questions related to running on AWS are: did they “re-design for failure,” and will their customers care about data sovereignty?
Cloud-Native (Design for Failure)
NetSuite’s CEO has been quoted as saying: ” From a service standpoint, if AWS goes down, what’s the first set of servers they’re going to bring up? I don’t think they’re Infor’s. It might be Netflix.” That shows how poorly he understands cloud and AWS: he confuses hosting with cloud. AWS does not get their customers servers back up, the customers do. The ones that are using AWS right let their software handle the failures gracefully. Applications that handle failures gracefully have been built with “design for failure” in mind and are considered “cloud-native.” Very few business-critical applications can be ported from traditional design, where they trust hardware not to fail, versus AWS’s cloud model, where it is the norm to have failures, and they have frequent brownouts that don’t count towards the 99.95% SLA. AWS’s scheduled or unscheduled maintenance and outages that last less than five minutes are not considered downtime. To be deemed as suffering an outage, Amazon EC2 customers need all of their running instances to be unreachable in more than one availability zone within the same region, with no ability to launch replacement instances. The 99.95% SLA means expecting 4.38 hours of unscheduled infrastructure downtime to affect an entire availability zone, lasting more than five minutes. Performance degradation, brownouts, and system reboots do not count as downtime! And if the software is designed to handle that type of unreliable system, it’s no harm, no foul.
Data Sovereignty and Clouds
Regulations and laws on data sovereignty should be carefully considered before selecting a cloud service provider. In the case of Infor’s customer base, it probably makes more sense to partner with regional providers that are owned and operated by residents of the country. Laws that mandate a company to keep a customer’s data in that customer’s home country are being promoted in countries around the world, especially since Edward Snowden’s revelations. A key consideration driving data sovereignty and the growth of regional clouds worldwide is the prevention of data from being subpoenaed by a foreign power. In September 2014, the US government ordered Microsoft to hand over data stored in its cloud in Dublin. While this violates Irish law, Microsoft’s not complying would mean breaking US law. Legitimate concerns such as this that are unresolved in the courts are driving the uncertainty around using foreign-owned public clouds.
After looking at Infor’s website, I think the author may have the wrong impression about Infor’s CloudSuite. It looks to me like Infor can run anywhere based on its customers’ technical and business requirements.
I doubt that Infor will lock itself into only delivering on AWS.
We built cloud.ca to handle both cloud-native and traditional workloads. It is a Canadian owned and operated virtual private cloud. Check it out today!
A checklist for your cloud migration
Download the white paper to get a step by step guide to a successful migration strategy.
Cloud migration one-pager
Everything you need to know about how our services can help get your cloud journey started.