By far the largest percentage of the total cost of software ownership is in operations. Here is a list of many capabilities that ISVs find they need to operate a SoOftware-As-Service solution successfully:
· Business
o Automated customer and end user account provisioning
o Usage metering, reporting and analytics by user and customer
o Automated billing and collections with usage detail
o Product cross-sell and up-sell during customer support calls
o Easy integration of third-party solutions to boost up-selling capabilities
· Operations
o Datacenter management
o Production application monitoring and administration
o System configuration management, fast server provisioning
o System performance analysis and capacity forecasting
o Firewalls, intrusion detection, data security
o Tier 1 and 2 customer support
o Disaster Recovery, including user and account level data backup/restore
o Data migration and transformation
o 24/7 break-fix support
o Controls for compliance with audit standards such as SAS 70, PCI, SOX, etc.
o SLA management
Many ISVs interesting in delivering SaaS will quickly decide that it is less expensive and more strategic to partner with a SaaS pure player hoster who can operate and support their production systems at peak efficiency and reliability.
SaaS is turning computing into a utility like the electric grid did for industry.
SaaS is a significant growth driver but fuzzy informations spread over the web make it difficult to understand and differenciate from software hosting environments.
This blog focuses on key success factors driving the development of a successful Business-As-A-Service solution.
SaaS is a significant growth driver but fuzzy informations spread over the web make it difficult to understand and differenciate from software hosting environments.
This blog focuses on key success factors driving the development of a successful Business-As-A-Service solution.
Showing posts with label architecture. Show all posts
Showing posts with label architecture. Show all posts
Sunday, September 13, 2009
Monday, July 27, 2009
A different conception of Software Development
Software-As-Service should not be treated as a technological or architectural topic.
SaaS should be seen as a prism through which usual ways of doing IT should be rethinked.
Take the example of Software development. I have been involved in software development for more than 25 years since my first programs in peek and poke Assembly language! At that period of time optimization of the software was not a recomandation it was mandatory. My first computer only had 1 Ko of RAM!
Then software started to being 'fat'. Why? Because developers and software editors did not care about using a lot of memory or disk space. Their manual had to say that to run this software you would need such hardware characteristics, and the user had to care about it! You did not get the latest computer, so do not blame me if your software runs slowly...
SaaS will eventually reverse this process.
SaaS involves software editors to run their software on virtualization platforms.
SaaS involves software editors to pay for those investments, and the power consumption is eating their margin if not taken seriously!
Until now we have seen a lot of new computer langages being invented, and a lot of web technologies too. I bet that the number of development langages and methodologies will lower and that this will not be a factor of richness diminution. End users will get more stable, more efficient and more adaptative programs if you give them the power of mashing-up the functions they need. To make that happen fficiently you need to simplify the way you develop and maintain a large common factor so that pieces developed by a large number of developer would fit together.
The HTML lego for software could be Web Services and the execution paradigm would be SaaS.
Why would you need to keep on developing web code? An application is better developed, stronger, more efficient, more reliable if developed on the basis of an operating system whatever it is. Webg is great for visualizing and interacting, for letting the end user mash-up and create their 'own' interface.
I bet that with SaaS the software editors will find it more efficient to develop software the way it was before - efficiently - and as 'heavy clients'. Then use the SaaS to virtualize those applications and let them run whenever and however the end users want to use them. Simply splitting up the 'heavy clients' into 'heavy functions' would be the path to follow. Each 'heavy function' being usable as a single piece, being integrable into whatever web interaction technology you would need, being insertable wherever you would need.
SaaS will help developers to reconnect with their users and this will radically transform the way we have seen the computing industry until today.
SaaS should be seen as a prism through which usual ways of doing IT should be rethinked.
Take the example of Software development. I have been involved in software development for more than 25 years since my first programs in peek and poke Assembly language! At that period of time optimization of the software was not a recomandation it was mandatory. My first computer only had 1 Ko of RAM!
Then software started to being 'fat'. Why? Because developers and software editors did not care about using a lot of memory or disk space. Their manual had to say that to run this software you would need such hardware characteristics, and the user had to care about it! You did not get the latest computer, so do not blame me if your software runs slowly...
SaaS will eventually reverse this process.
SaaS involves software editors to run their software on virtualization platforms.
SaaS involves software editors to pay for those investments, and the power consumption is eating their margin if not taken seriously!
Until now we have seen a lot of new computer langages being invented, and a lot of web technologies too. I bet that the number of development langages and methodologies will lower and that this will not be a factor of richness diminution. End users will get more stable, more efficient and more adaptative programs if you give them the power of mashing-up the functions they need. To make that happen fficiently you need to simplify the way you develop and maintain a large common factor so that pieces developed by a large number of developer would fit together.
The HTML lego for software could be Web Services and the execution paradigm would be SaaS.
Why would you need to keep on developing web code? An application is better developed, stronger, more efficient, more reliable if developed on the basis of an operating system whatever it is. Webg is great for visualizing and interacting, for letting the end user mash-up and create their 'own' interface.
I bet that with SaaS the software editors will find it more efficient to develop software the way it was before - efficiently - and as 'heavy clients'. Then use the SaaS to virtualize those applications and let them run whenever and however the end users want to use them. Simply splitting up the 'heavy clients' into 'heavy functions' would be the path to follow. Each 'heavy function' being usable as a single piece, being integrable into whatever web interaction technology you would need, being insertable wherever you would need.
SaaS will help developers to reconnect with their users and this will radically transform the way we have seen the computing industry until today.
Labels:
architecture,
ISVs,
marketing,
messaging,
positioning,
strategy
Sunday, February 1, 2009
ISVs need to host their applications on a SaaS dedicated hosting platform



The SaaS Hoster provides infrastructure & personnel resources with a highly variable cost structure – you are only paying for what you need / use.
This cost structure provides a best-of-breed solution at a predictable, competitive price.
If the SaaS Hoster uses a fully virtualized platform he provides a power on-demand ressource to the ISV who then pays a fee proportional to the size of the customers he currently serves.
ISVs also want to grab the opportunities offered by a SaaS integration with other ISV's applications:
- Integrate their application with others to increase the customer's perceived value;
- Cross-sale part of their application with other ISVs as a SaaS royalty business model;
- Allow resellers to create bundles of already integrated and working sets of applications.
Subscribe to:
Posts (Atom)