The temperature has cooled down here in North America and winter is around the corner. It is still relatively warm and in the cold weather it's nice to write about some warmness, which is SaaS! Sure, everyone knows the latest success of Workday. The question is why or how SaaS is succeeding in the marketplace? This may not be true for all applications but definitely business applications are going towards SaaS model.
- Runtime Environment
I will highlight the CIO panel here and if you want to hear more about the summit, please ping me separately. (uday dot s at-sign comcast dot net)
There were 4 CIO's from big corporations. The moderator started the discussion asking about what % of applications are SaaS today? The answer was 90%, 50%, 25% and 20%. Then moderator said it makes sense to ask first 20% and 25% CIOs about SaaS adoption. For everyone's surprise they both said they are going to adopt SaaS aggressively in next few years!
- 20% CIO
- I am sick of having repeated discussion with CFO about "do more with less". If it is SaaS, its just a binary discussion. I just need to pick the right vendor. I am also sick of dealing with servers to DBA!
- 25% CIO
- I don't expect any IT application developers in my organization in 5 years from now. They will be doing something else!
- 50% CIO
- He was interesting. His acceleration from here onwards going to be cautious. He is taking safer approach/too much legacy and will have hybrid environment. But he was super supportive of SaaS too.
- 90% CIO
- He said, don't ask me when is the next 10%. I am just wearing CIO hat for this panel as my official title is already changed! I don't have any legacy and so it was easy for me to take SaaS route from the beginning.
- Support of SaaS model.
- Need to handle legacy environment and migration is taking time.
- SaaS integration is painful even today. We need a solution that can integrate many SaaS apps.
- Not outsourcing Active Directory any time soon.
- BYOD is real.
OK. Lets get back to the 3 factors that I highlighted in the beginning of this article.
- Runtime Environment
- Before, the product team builds a software product on a particular OS. Then they have to port to different OS to support wider market. This is pain.
- Now, the software products are distributed applications. It no longer runs on a single desktop or a single server. You have a complex network environment with distributed servers and storage systems as runtime environment. It is not an easy task to reproduce the application in another environment for deployment. This is more painful. Here is an example of politely saying 'no': http://bit.ly/U3RN9C
- The summary is "single runtime environment" is a blessing for product teams in SaaS. It is even more blessing for IT team as they don't have to deal with software upgrades as there is no software in the first place!
- In the past, all software product teams have to deal with sample applications and seed-data to perfect their software. Then they will discover "real bugs" in the customer environment! Then release service pack after service pack to fix bugs. It was a painful experience from product teams to marketing to sales to customers.
- In the SaaS model, product team gets "real data" and "real use cases". Then they discover bugs in their own backyard (data center) and quickly fix it. The pain stays with the product team itself and nature forces them to perfect the application quickly!
- The enterprise is increasingly accepting BYOD for accessing any-service, any-time, any-where in any-device model. This model aligns well with SaaS than behind the IT firewall with VPN challenges.
- In 2000: Why enterprise software is not like Amazon.com?
- In 2009: Why enterprise software is not like Facebook.com?