This is certainly well-deserved praise given the proven ability of ServiceNow to disrupt a market segment previously dominated by the biggest players in the space.
The article also discusses ServiceNow’s architecture and asks if it is “real or “marketecture?” ServiceNow’s penetration into many of the largest enterprises in the world is surely proof that these customers simply don’t care. However, should ServiceNow be concerned about continued growth and a rapidly expanding infrastructure to manage under their single tenant, or as they phrase it, “multi-instance” architecture?
It may be reasonable to reopen the multi-tenant vs multi-instance argument — once again. It is difficult to ignore the comparison that the article boldly leads with in its title:
“Analysis: ServiceNow Cloud “The New Sheriff in IT Town” – The Workday and Salesforce of IT Service Automation”
In the Forbes article, Mr. Furrier states “Specifically, from a customer standpoint the single vs multi-tenant argument is irrelevant.”
But, on its website, Salesforce takes this position:
Is the service truly multi-tenant?
Leading Web applications such as Gmail and eBay run on a single code base and infrastructure shared by all users. Multitenant architecture allows for quick deployment, lower cost, and faster innovation. Single-tenant systems are not designed for large-scale on-demand success. The internal inefficiencies of maintaining separate physical infrastructure for each customer makes it impossible for vendors to deliver a quality service and innovate quickly. Make sure the vendor’s architecture enables:
Efficient service delivery, with low maintenance and upgrade burden
Consistent performance and reliability based on manageable multitenant architecture
Rapid product release cycles
Similarly, Workday on its website says this:
One line of code and always up to date. A single version of Workday exists across all customers. That’s the real cloud. Anything else is an imposter.
Every customer is on the same version of Workday. That means no customer is left behind when the software is updated. And when everyone is on the same version, the result is a community with unprecedented levels of communication and collaboration.
So, who is right? I’ll leave that for you to debate.