The Hub Commentary_
I feel like changing things up here in Business Service Management land today. This blog caught my attention as it describes the leap of going from an independent software vendor (ISV) to a SaaS offering. It has challenges in how the software is architected so that it can then later be hosted and ultimately used by many customers in a single, multi-tenant environment to take full advantage of the economies of scale. The fact is most are run in dedicated environments to short cut this challenge.
The piece I find curious and would debate is why should an ISV turn into the service provider? I would be highly speculative of these situations as most lack the experience to make that leap to manage a data center. Best to partner with a hosting provider with th expertise in managing and running software and stick to what you know best – the application.
Now relating this back to the topic of Business Service Management, the application needs to be instrumented or as I call it, service enabled. Data needs to be sent to the monitoring and management technology to provide basic health and availability and thus the need for that middleware testing the performance of the hosting provider as well as application performance data. The cloud and service provider models bring great agility, but all point to the requirement for an integration platform to provide that end-to-end service view.
How are you measuring your service providers?
Sinclair’s recent post Cloud Middleware: The Language Shared by Network Engineers and Developers posits that the cloud space has seemingly maintained a bias towards infrastructure offerings (IaaS) and is now at an “inflection point” where a common layer – the cloud middleware layer – will be required by developers and network managers alike to, as Jeff Kaplan puts it: Bridge the Great Divide in Cloud Computing. I’d like to expand on this theme. (Read Full Article…)