Yesterday I took part in an implementing design course. At the course was a systems architect from a large-ish software company. Morning tea came around and I started talking to him and, as is my norm, started waxing poetic about Sass. He proceeded to tell me that one of their products constitutes SaaS because, although it is installed on server within the organisation, from th users perspective it has all the appearances of SaaS;
- It is updated centrally by someone else
- They just use it and don’t need to think about updates, sysadmin etc
My initial thought was, no way, a core tenet of SaaS is its existence in the clouds… or is it. AIR is blurring the distinction a little bit, and from a users perspective at least, the issue is solution-centric rather than falling into a defined and detailed list of traits.
But then again if we define SaaS this loosely we run the risk of losing any real identity for it as a class of product.
No – I’m still sticking with SaaS needing to be (in the main part) hosted in the clouds.
What about you(se)?