Software as a service


Software as a service

Software as a service (SaaS, typically pronounced 'sass') is a model of software deployment where an application is hosted as a service provided to customers across the Internet. By eliminating the need to install and run the application on the customer's own computer, SaaS alleviates the customer's burden of software maintenance, ongoing operation, and support. Conversely, customers relinquish control over software versions or changing requirements; moreover, costs to use the service become a continuous expense, rather than a single expense at time of purchase. Using SaaS also can "conceivably" reduce that up-front expense of software purchases, through less costly, on-demand pricing. From the software vendor's standpoint, SaaS has the attraction of providing stronger protection of its intellectual property and establishing an ongoing revenue stream. The SaaS software vendor may host the application on its own web server, or this function may be handled by a third-party application service provider (ASP). This way, end users may reduce their investment on server hardware too.

Architecture

History

The concept of "software as a service" started to circulate prior to 1999 and was considered to be "gaining acceptance in the marketplace" in Bennett et al., 1999 paper on "Service Based Software" [ [http://www.bds.ie/Pdf/ServiceOriented1.pdf Service Based Software, Bennet et al. 1999] ] .

Whilst the term "software as a service" was in common use, the CamelCase acronym "SaaS" was allegedly not coined until several years later in a white paper called "Strategic Backgrounder: Software as a Service" [ [http://www.siia.net/estore/ssb-01.pdf Strategic Backgrounder: Software as a Service] ] by the Software & Information Industry's eBusiness Division published in Feb. 2001, but written in fall of 2000 according to internal Association records.

Philosophy

As a term, SaaS is generally associated with business software and is typically thought of as a low-cost way for businesses to obtain the same benefits of commercially licensed, internally operated software without the associated complexity and high initial cost. Consumer-oriented web-native software is generally known as Web 2.0 and not as SaaS. Many types of software are well suited to the SaaS model, where customers may have little interest or capability in software deployment, but do have substantial computing needs. Application areas such as Customer relationship management (CRM), video conferencing, human resources, IT service management, accounting, web analytics, web content management and e-mail are some of the initial markets showing SaaS success. The distinction between SaaS and earlier applications delivered over the Internet is that SaaS solutions were developed specifically to leverage web technologies such as the browser, thereby making them web-native. The data design and architecture of SaaS applications are specifically built with a 'multi-tenant' backend, thus enabling multiple customers or users to access a shared data model. This further differentiates SaaS from client/server or 'ASP' (Application Service Provider) solutions in that SaaS providers are leveraging enormous economies of scale in the deployment, management, support and through the Software Development Lifecycle.

Key characteristics

The key characteristics of SaaS software, according to IDC, include:cite web| title=2005 Software as a Service Taxonomy and Research Guide| first=Erin| last=Traudt| coauthors=Amy Konary| url=http://www.idc.com/getdoc.jsp?containerId=33453&pageType=PRINTFRIENDLY#33453-S-0001| accessdate=2006-08-25| year=2005| month=June| publisher=IDC| pages=7] Dead link|date=May 2008

* network-based access to, and management of, commercially available software
* activities that are managed from central locations rather than at each customer's site, enabling customers to access applications remotely via the Web
* application delivery that typically is closer to a one-to-many model (single instance, multi-tenant architecture) than to a one-to-one model, including architecture, pricing, partnering, and management characteristics
* centralized feature updating, which obviates the need for downloadable patches and upgrades.
* SaaS is often used in a larger network of communicating software - either as part of a mashup or as a plugin to a platform as a service. Service oriented architecture is naturally more complex than traditional models of software deployment.

SaaS applications are generally priced on a per-user basis, sometimes with a relatively small minimum number of users and often with additional fees for extra bandwidth and storage. SaaS revenue streams to the vendor are therefore lower initially than traditional software license fees, but are also recurring, and therefore viewed as more predictable, much like maintenance fees for licensed software.

Implementation

According to Microsoft, SaaS architectures generally can be classified as belonging to one of four "maturity levels," whose key attributes are configurability, multi-tenant efficiency, and scalability.cite web| title=Architecture strategies for catching the long tail| url=http://msdn2.microsoft.com/en-us/library/aa479069.aspx| accessdate=2008-05-24 | year=2006| month=April] Each level is distinguished from the previous one by the addition of one of those three attributes:

* Level 1 - Ad-Hoc/Custom: At the first level of maturity, each customer has its own customized version of the hosted application and runs its own instance of the application on the host's servers. Migrating a traditional non-networked or client-server application to this level of SaaS typically requires the least development effort and reduces operating costs by consolidating server hardware and administration.

* Level 2 - Configurable: The second maturity level provides greater program flexibility through configurable metadata, so that many customers can use separate instances of the same application code. This allows the vendor to meet the different needs of each customer through detailed configuration options, while simplifying maintenance and updating of a common code base.

* Level 3 - Configurable, Multi-Tenant-Efficient: The third maturity level adds multi-tenancy to the second level, so that a single program instance serves all customers. This approach enables more efficient use of server resources without any apparent difference to the end user, but ultimately is limited in its scalability.

* Level 4 - Scalable, Configurable, Multi-Tenant-Efficient: At the fourth and final SaaS maturity level, scalability is added through a multitier architecture supporting a load-balanced farm of identical application instances, running on a variable number of servers. The system's capacity can be increased or decreased to match demand by adding or removing servers, without the need for any further alteration of application software architecture.

Virtualization also may be used in SaaS architectures, either in addition to multi-tenancy, or in place of it. [cite web| title=Workstream prefers virtualization to multi-tenancy| url=http://blogs.zdnet.com/SAAS/?p=400| accessdate=2008-05-24 | year=2007| month=October| first=Phil| last=Wainewright] One of the principal benefits of virtualization is that it can increase the system's capacity without additional programming. On the other hand, a considerable amount of programming may be required to construct a more efficient, multi-tenant application. Combining multi-tenancy and virtualization provides still greater flexibility to tune the system for optimal performance. [cite web| title=Multi-tenancy and Virtualization | url=http://blogs.msdn.com/fred_chong/archive/2006/10/23/multi-tenancy-and-virtualization.aspx | accessdate=2008-05-24 | year=2006 | month=October| first=Fred | last=Chong] In addition to full operating system-level virtualization, other virtualization techniques applied to SaaS include application virtualization and virtual appliances.

Various types of software components and frameworks may be employed in the development of SaaS applications. These tools can reduce the time to market and cost of converting a traditional on-premise software product or building and deploying a new SaaS solution. Examples include components for subscription management, grid computing software, web application frameworks, and complete SaaS platform products. [cite web| title=Repealing the SaaS Tax| url=http://itmanagement.earthweb.com/article.php/3663266| accessdate=2008-05-24 | year=2007| month=March| first=Sinclair| last=Schuller]

Adoption

Drivers

The traditional rationale for outsourcing of IT systems is that by applying economies of scale to the operation of applications, a service provider can offer better, cheaper, more reliable applications than companies can themselves.The use of SaaS-based applications has grown dramatically, as reported by many of the analyst firms that cover the sector. But it’s only in recent years that SaaS has truly flourished. Several important changes to the way we work have made this rapid acceptance possible.
*Everyone has a computer: Most information workers have access to a computer and are familiar with conventions from mouse usage to web interfaces. As a result, the learning curve for new, external applications is lower and less hand-holding by internal IT is needed.
*Computing itself is a commodity: In the past, corporate mainframes were jealously guarded as strategic advantages. More recently, the applications were viewed as strategic. Today, people know it’s the business processes and the data itself—customer records, workflows, and pricing information—that matters. Computing and application licenses are cost centers, and as such, they’re suitable for cost reduction and outsourcing. The adoption of SaaS could also drive Internet-scale to become a commodity. [http://www.saasblogs.com/2006/09/26/scale-as-a-commodity-2/ SaaSBlogs: Scale as a Commodity]
*Insourcing IT systems requires expensive overhead including salaries, health care, liability and physical building space.
*Applications are standardized: With some notable, industry-specific exceptions, most people spend most of their time using standardized applications. An expense reporting page, an applicant screening tool, a spreadsheet, or an e-mail system are all sufficiently ubiquitous and well understood that most users can switch from one system to another easily. This is evident from the number of web-based calendaring, spreadsheet, and e-mail systems that have emerged in recent years.
*Parametric applications are usable: In older applications, the only way to change a workflow was to modify the code. But in more recent applications—particularly web-based ones—significantly new applications can be created from parameters and macros. This allows organizations to create many different kinds of business logic atop a common application platform. Many SaaS providers allow a wide range of customization within a basic set of functions.
*A specialized software provider can target global markets: A company that made software for human resource management at boutique hotels might once have had a hard time finding enough of a market to sell its applications. But a hosted application can instantly reach the entire market, making specialization within a vertical not only possible, but preferable. This in turn means that SaaS providers can often deliver products that meet their markets’ needs more closely than traditional “shrinkwrap” vendors could.
*Web systems are reliable enough: Despite sporadic outages and slow-downs, most people are willing to use the public Internet, the Hypertext Transfer Protocol and the TCP/IP stack to deliver business functions to end users.
*Security is sufficiently well trusted and transparent: With the broad adoption of SSL organizations have a way of reaching their applications without the complexity and burden of end-user configurations or VPNs.
*Availability of enablement technology: According to IDC,cite web| title=2005 Software as a Service Taxonomy and Research Guide| first=Erin| last=Traudt| coauthors=Amy Konary| url=http://www.idc.com/getdoc.jsp?containerId=33453&pageType=PRINTFRIENDLY#33453-S-0005| accessdate=2006-08-25| year=2005| month=June| publisher=IDC| pages=7] organizations developing enablement technology that allow other vendors to quickly build SaaS applications will be important in driving adoption. Because of SaaS' relative infancy, many companies have either built enablement tools or platforms or are in the process of engineering enablement tools or platforms. A Saugatuck study shows that the industry will most likely converge to three or four enablers that will act as SaaS Integration Platforms (SIPs).cite web| title=SaaS 2.0: Saugatuck Study Shows Rapid SaaS Evolution to Business Platforms| url=http://pdfserver.prweb.com/pdfdownload/377561/pr.pdf#search=%22saugatuck%20%20sip%20saas%20filetype%3Apdf%22.| accessdate=2006-09-01 | year=2006| month=April]
* Wide Area Network's bandwidth has grown drastically following Moore's Law (more than 100% increase each 24 months) and is about to reach slow local networks bandwidths. Added to network quality of service improvement this has driven people and companies to trustfully access remote locations and applications with low latencies and acceptable speeds.

Limiting factors

Widespread implementation of SaaS requires that the services be well defined. That can achieve an economy of scale and the capacity to balance supply and demand. This assumption holds true for those areas of IT that are ubiquitous, a cost of doing business and commodity-like. SaaS is therefore not suitable for innovative or highly specialized niche systems, though SaaS may be used to provide one or more components in such systems.

As with manufacturing, a lack of substitutability and second sourcing options with any commodity creates a strategic weakness for any customer in terms of security, competition and pricing. Various forms of this "weakness", such as 'vendor lock-in', are often cited as a barrier to adoption of SaaS as the current industry lacks portability and interoperability between vendors. This means that to change from one vendor to another will take a considerable amount of effort and time. This situation is resolvable by the introduction of open sourced standards and the development of markets based upon such standards.

Whilst the severe lack of substitutability is unresolved, many vendors counter the concerns over potential security and operational risk with the argument that the professionals operating SaaS applications may have much better security and redundancy tools available to them.

Furthermore the concern that SaaS applications pose some difficulty for businesses that need extensive customization is countered with the claim that many vendors have made progress with both customization and publication of their programming interfaces. It should be noted that customization will reduce substitutability and given that SaaS covers commodity-like activities, the strategic benefit of customization is highly dubious.

In addition to this, the availability of open source applications, inexpensive hardware and low cost bandwidth combine to offer compelling economic reasons for businesses to operate their own software applications, particularly as open source solutions have become higher quality and easier to install.

ales Channels

With products below the $100 range and its focus on the mid market, direct selling can become an expensive undertaking. SaaS companies are seeking alternatives by selling through value-added resellers (VARs), Managed Service Providers (MSPs), Master Managed Service Providers (MMSPs) and similar alliance partners. But since SaaS is not only a different delivery mechanism but a different business model and different technology as well, selling through channels has its own challenges.

See also

* Service bureau
* Application service provider
* Cloud computing
* Everything as a service
* Data as a service
* Grid computing
* Master Managed Service Provider
* Mobile enterprise
* Online office suite
* SaaS platform
* Secure Virtual Office
* Software plus services
* Supply chain
* Utility computing

References

External links

Look at other dictionaries:

  • Software as a Service — Software as a Service, kurz SaaS, ist ein Teilbereich des Cloud Computings. Das SaaS Modell basiert auf dem Grundsatz, dass die Software und die IT Infrastruktur bei einem externen IT Dienstleister betrieben und vom Kunden als Service genutzt… …   Deutsch Wikipedia

  • Software as a service — (SaaS) («Программное обеспечение как услуга»), или Software on Demand (SoD) («Программное обеспечение по требованию»)  бизнес модель продажи программного обеспечения, при которой поставщик разрабатывает веб приложение и самостоятельно… …   Википедия

  • Software as a service — Logiciel en tant que service Le logiciel en tant que service ou en anglais le Software as a Service (SaaS) est un concept consistant à fournir des services ou des logiciels informatiques par le biais du Web et non plus dans le cadre d une… …   Wikipédia en Français

  • Software As A Service - SaaS — A cloud computing approach to providing users with computer applications. Instead of each user having to install the software on his computer, the user is able to access the program via the internet. Businesses commonly use software as a service… …   Investment dictionary

  • Service-oriented architecture — (SOA) is a method for systems development and integration where functionality is grouped around business processes and packaged as interoperable services . SOA also describes IT infrastructure which allows different applications to exchange data… …   Wikipedia

  • Service Oriented Programming — (SOP) is a programming paradigm that uses services as the unit of computer work, to design and implement integrated business applications and mission critical software programs. Services can represent steps of business processes and thus one of… …   Wikipedia

  • Software plus services — [ [http://msdn2.microsoft.com/en us/architecture/aa699384.aspx Software + Services (S+S) ] ] describes the idea of combining hosted services with capabilities that are best achieved with locally running software. It describes composite… …   Wikipedia

  • Software development process — Activities and steps Requirements Specification …   Wikipedia

  • Software on demand — (dt. Software auf Nachfrage) ist ein Service bei dem der Kunde eine bestimmte Software bei dem Anbieter betreiben lässt, der diese auch je nach Anfrage (on Demand) skaliert. Dieses erlaubt flexible Lizenzierungsformen, bei dem nach Datenvolumen,… …   Deutsch Wikipedia

  • Software como servicio — (del inglés: Software as a Service, SaaS) es un modelo de distribución de software donde el software y los datos que maneja se alojan en servidores de la compañía de tecnologías de información y comunicación (TIC) y se accede con un navegador web …   Wikipedia Español


Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”

We are using cookies for the best presentation of our site. Continuing to use this site, you agree with this.