Saas

Only available on StudyMode
  • Download(s) : 74
  • Published : December 12, 2012
Open Document
Text Preview
white paper

> SaaS

architecture

www.progress.com

table of contentS
1.0 introduction . . . . . . . . . . . . . . . . . . . 2.0 SaaS evolution . . . . . . . . . . . . . . . . . 2.1 SaaS Definition . . . . . . . . . . . . . . . . . 2.2 SaaS Four Waves Evolution Model . . . . . . 3.0 Distributed application architecture . . . . 3.1 User Tier . . . . . . . . . . . . . . . . . . . . 3.2 Application Tier. . . . . . . . . . . . . . . . . 3.3 Data Access Tier . . . . . . . . . . . . . . . . 3.4 Data Storage Tier . . . . . . . . . . . . . . . 4.0 SaaS architecture . . . . . . . . . . . . . . . 4.1 Distribution Tier . . . . . . . . . . . . . . . . 4.2 Other Application Tier Components . . . . . . 4.3 Administration . . . . . . . . . . . . . . . . . 4.4 Infrastructure Monitoring . . . . . . . . . . . 4.5 Configuration . . . . . . . . . . . . . . . . . . 5.0 SaaS reference architecture components 5.1 SaaS Architecture . . . . . . . . . . . . . . . 5.2 SaaS Operations . . . . . . . . . . . . . . . . 6.0 Summary . . . . . . . . . . . . . . . . . . . . 7.0 references . . . . . . . . . . . . . . . . . . . 8.0 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 . 1 . 1 . 2 . 4 . 5 . 5 . 6 . 6 . 6 . 7 . 8 . 9 .11 .12 .13 .13 .15 .15 .16 .17

www.progress.com

1

1.0 introDuction
Software-as-a-Service (SaaS) is emerging as a dominant approach to delivering software. In addition to being an application delivery model, it is also a business model. Accordingly, SaaS encompasses a broad spectrum of business, marketing and technical opportunities, issues and challenges. This paper focuses on the technical aspects of SaaS and provides an overview of the technical architectural components. We begin this paper with a discussion of the evolution of SaaS, including a foundational definition and an overview of Saugatuck Technology’s Four Waves evolutionary concept. We then cover the main components of a distributed application architecture followed by extensions to this architecture that define a more comprehensive and mature SaaS implementation. Finally, the paper presents a series of SaaS reference architecture concepts. These components are explored in more detail in a series of supporting papers.

2.0 SaaS evolution
2.1 SaaS Definition Software-as-a-Service (SaaS) shares the distinction of being both a business model and an application delivery model. SaaS enables customers to utilize an application on a pay-as-you-go basis and eliminates the need to install and run the application on the customer’s own hardware. Customers generally access the application via a Web browser or thin client over the Internet. SaaS is most often subscription-based and all ongoing support, maintenance, and upgrades are provided by the software vendor as part of the service. Application customization capabilities, if available at all, are generally provided to all customers in a consistent manner. From the perspective of the software vendor, the SaaS model provides stronger protection of its intellectual property, operational control of the environment running the software, and generally a repeatable revenue stream from the service subscription fees. Software vendors have varying capabilities and applications can come in varying flavors but SaaS applications most typically support many unique customers using a single instance of that application– also known as multi-tenancy. www.progress.com

2

2.2 SaaS four WaveS evolution MoDel In a 2007...
tracking img