The document discusses Software as a Service (SaaS) and the architectural considerations for developing SaaS applications. It covers the key aspects of SaaS including multi-tenancy, customization, scalability, and monetization options. The document also outlines some common architectural patterns for SaaS including using a shared database with customizable fields, meta-data services to manage customizations, and stateless and scalable application design.
6. Realizing SaaS Software Services Business Model Application Architecture Operational Structure
7. SaaS impacts the entire consumption cycle : In particular in the L.O.B. application space Purchase Deployment Management From : Long Eval Process CapEx To : Try before you buy OpEx From : Customization To : Configuration From : Reliance on internal IT To : SLAs Enable: Try before you buy Enable : Configuration (no custom code) Enable : SLA monitoring / enforcement Buyer Seller
8. Big Deal 1: Importance of Economy of Scale Hardware Cost at Provider People Cost at Provider
14. “ Basic” SaaS Maturity Model Ad-hoc / Custom Application Hosting Model (ASP) Configurable (but single tenant) Physical or Virtual Isolation Configurable, Multi tenant Scalable, Configurable, Multi tenant
15.
16. High Level Application Architecture Browser Smart Client Presentation Process Services Business Services Meta Data Services Security Services Directory Service Databases File System Meta Data
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28. Shared Services “ Classic” Hosting CPU-Storage-Bandwidth As provider: do you build or buy the hosting? Shared Services: e.g. Billing, Metering, SLA Monitoring… a.k.a. SO Infra, Service Delivery Platform, OSS/BSS “ Classic” Hoster SaaS Hoster SaaS Provider