In preparing the recent ebizQ article on BPM and cloud computing available on ebizQ, as you may know, if you read my blogs posts, I was a skeptic about cloud computing as not being much different than the service bureaus, or Software-as-a-Service (SaaS), application service provision, and whatever buzzword fits in your generation.
But basically, with the help of Fujitsu and some others that I interviewed, I was convinced that at least in terms of BPM, the cloud can make a difference. The key is that the BPM software or service you choose should be architected in such as way as to take advantage of the cloud computing choice you are making. Presumably, software is more functional if it is designed or redesigned to run in the cloud as opposed to simply taking advantage of the cloud's business model--typically SaaS--or the cloud's telecommunications characteristics.
So I thought it made sense to ask one of the sources that helped me on the article, Rajiv Onat, Senior Product Manager of Interstage at Fujitsu, to join me in a podcast to explain some of these fine points that we just can't get across when we're doing a round-up feature article.
In the podcast, Rajiv makes the point that when you look at cloud models, there are three varieties to consider:
- the public cloud
- the private cloud
- the hybrid cloud
In these three different models, the deployment options differ. From a public cloud offering perspective, you're looking at a classic multi-tenancy as with any SaaS application in a third-party hosting environment. From a private cloud perspective, you're looking at a single-tenant but multiple-application scenario. And from a hybrid model, you're looking at a combination of both. The issue is to make sure your BPM choice's architecture matches the cloud computing choice you are making (some support all three).
The podcast lasts about 9 minutes.
-- Dennis Byron
(See more about BPM in Cloud Computing and Fujitsu's offering in particular in a playback of ebizQ's Cloud Camp.)
Leave a comment