Software as a Service – or Software plus Services?

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

There’s a lot of media buzz right now about cloud computing – which encompasses both “web 2.0” and Software as a Service (SaaS). Whilst it’s undeniable that web services are becoming increasingly more important, I’ll stand by my comments from a couple of years ago that the “webtop” will not be in mainstream use any time soon and those who are writing about the the death of Microsoft Windows and Office are more than a little premature.

Even so, I was interested to hear Microsoft’s Kevin Sangwell explain the differences between SaaS and the Microsoft idea of software plus services (S+S) during the recent MCS Talks session on infrastructure architecture.

I’ve heard Microsoft executives talk about software plus services but Kevin’s explanation cut’s through the marketing to look at what S+S really means in the context of traditional (on premise) computing and SaaS:

Kevin made the point that there is actually a continuum between on premise and SaaS solutions:

Software delivery continuum and software services taxonomy

  • We all understand the traditional software element – where software is installed an operated in-house (or possibly using a managed service provider).
  • Building block services are about using web services to provide an API to build applications “in the cloud” – so Amazon’s simple storage service (S3) is an example. This gives developers something to hook into and onto which to deliver a solution – for example, Jungle Disk uses the Amazon S3 platform to provide online storage and backup services.
  • Attached services provide self-contained functionality – for example anti-spam filtering of e-mail as it enters (or exits) an organisation.
  • Finished services are those that operate entirely as a web service – with being one, often quoted, example – Google Apps would be another (not that Microsoft are ever likely to promote that one…).

S+S is about creating a real-world hybrid – not just traditional or cloud computing but a combination of software and services – for example an organisation may use a hosted Exchange Server service but they probably still use Microsoft Outlook (or equivalent software) on a PC.

So, would moving IT services off to the cloud make all the associated IT challenges disappear? Almost certainly not! All this would lead to is a disjointed service and lots of unhappy business users. SaaS and S+S do not usually remove IT challenges altogether but they replace them with new ones – typically around service delivery (e.g. managing service level agreements, integrating various operational teams, etc.) and service support (e.g. presenting a coherent service desk with appropriate escalation between multiple service providers and the ability to assess whether a problem relates to internal IT or the hosted service) but also in relation to security (e.g. identity lifecycle management and information rights management).

Kevin has written an article for The [MSDN] Architecture Journal on the implications of software plus services consumption for enterprise IT and, for those who are interested in learning more about S+S, it’s worth a read.

7 thoughts on “Software as a Service – or Software plus Services?

  1. The cynic in me – must try hard to not be a cynic – says S+S is Microsoft’s counter against google’s SaaS offering. Everyone needs and wants to retain their own seperate AD infrastructure, client, server and application licence model? Rather than just log into an OS agnostic SaaS provider, don’t they?

    (I realise that google’s offering is immature).

  2. Hi Mike – I’m equally not sure that S+S is the “one true way” (for the reasons you state); but I’m mindful that not everyone will be prepared to trust their data to the cloud and for that reason most corporates will lean towards a hybrid model – closer to S+S than to SaaS (except in a few niche areas of their infrastructure).

    I’m seriously considering using Google Apps for my business – but I’m a one man band and I wouldn’t suggest it to any of my enterprise customers. In fact, I’m not convinced that anyone other than small-medium businesses and cash-strapped schools, charities, etc. will follow the SaaS route in it’s entirety (and it’s probably off limits for government departments – both local and central – as they will struggle to get around the various security restrictions).

    Only time will tell and I figure that this is another case where one size certainly doesn’t fit all.

    The main point was that this is the first time I’ve heard S+S described in a coherent manner – rather than as a load of marketing rhetoric!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.