Software-as-a-Service (SaaS): A Comprehensive Study of Cloud Service Models, Slides of Computer Networks

Download Software-as-a-Service (SaaS): A Comprehensive Study of Cloud Service Models and more Slides Computer Networks in PDF only on Docsity!

A Study of Cloud Service Model-

Software-as-a-Service (SaaS)

Understanding SAAS

 (^) A good way to understand the SaaS model is by thinking of a bank, which protects the privacy of each customer while providing service that is reliable and secure—on a massive scale.  (^) Multitenant Architecture  (^) Easy Customization  (^) Better Access

SaaS Maturity Model

Level 0 : (AdHoc

/Custom)

At its level, support multiple customers are served different copies of the software.

Adhoc/Custom Features

• (^) Each customer has a dedicated instance of the

software.

• (^) Customizations are made for each customer's specific

requirements.

• (^) Maintenance and updates are done individually for

each instance.

• (^) Can be resource-intensive in terms of development

and maintenance.

• (^) May lack scalability and efficiency due to the bespoke

nature of each instance.

Level 1 : (Configurable)  (^) In this level, there is a vendor (home owner) and a customer (tenant) involved. The vendor hosts a separate instance of the application for each customer. In this level all instances use the same code implementation, and the vendor meets customers needs by providing detailed configuration options that allow the customer to change how the application looks and behaves to its users. The changes made by tenant may allows availability of various options of customization to his customer.

Configurable/customer Features

 Customers can adjust settings and configurations without

altering the core code.

 Each customer still has their own instance of the software.

 Configurations are typically done through user-friendly

interfaces or administrative tools.

 Maintenance and updates are easier compared to the ad

hoc custom model.

 Offers more standardization while still allowing for some

level of individuality.

Level 2 : (Configurable multi-tenant efficient) At this level. the application architecture includes the multi tenancy concepts. Similar to level 1, the UI can be customizable per tenant. The customization per tenant is fully performed through configuration and is performed through a self- service tool, getting around the need of provider intervention.

Configurable/customer Features

 Multiple customers share a single instance of the software

(multi-tenancy).

 Customers can still configure settings and features to suit

their needs.

 Each customer's data and configurations are logically

separated for security and privacy.

 Maintenance and updates are done centrally, benefiting

all customers simultaneously.

 More efficient resource utilization compared to separate

instances for each customer.

Level 3:(Scalable, configurable multi- tenant efficient) The fourth and final SaaS maturity level adds scalability through a multitier architecture supporting a load-balanced farm of identical application instances, running on a variable number of servers. The provider can increase or decrease the system’s capacity to match demand by adding or removing servers, without the need for any further alteration of application software architecture.

Configurable/customer Features

 Highly scalable architecture to accommodate growth and

demand.

 Customers can configure settings and features as

needed.

 Efficient multi-tenancy ensures optimal resource

utilization.

 Robust security measures to ensure data isolation and

privacy.

 Centralized management for updates, maintenance, and

support.

SaaS Provider’s

Responsibilities

 (^) Responsible for running and managing servers, power and cooling, network access, data center space etc.  (^) SaaS also maintain operating system software, databases, installation of updates, ongoing backups, and more.  (^) Deploy web based applications to easily provision software for customers on demand.  (^) Use virtualization infrastructure (network, application, dev. platform, server, storage).

SaaS Provider’s Responsibilities….. Have well defined service level agreements with customers  (^) Provide the latest version of the application software to the customer. Ensuring the security and privacy of client data.  (^) Have the ability to gather comprehensive information about flaws, performance and usage patterns to improve their product.  (^) Responsible to deliver reliable and secure services according to requirement of their customers.

Challenges of

Implementing SaaS

Multi-tenant Deployment  (^) Scalability  (^) Reliability  (^) Data Security  (^) Integration

Conclusions

By integrating all of the application software, data center, database, IT infrastructure and services together in a web-based, multi-tenant on demand delivery model, SaaS vendors can provide assurance to customers with economies of and skill that was one of the biggest challenges for traditional, on- premise deployments. SaaS shifts the onus of deployment, operation, management, support and successfully operation of the application from the customer to the vendor. With the maturation of Software as a Service, we can expect to see more hybrid architectures, revenue generating opportunities, service offering, pricing models and rich set of applications. The biggest challenge for SaaS would be to gain customer’s confidence and it can be achieved by implementing efficient application-level security mechanism, with proper definition of SLA guarantees and many more. However SaaS has tremendous potential to meet growing demand for business, industries and entire economics.