CLOUD COMPUTING

FROM: RAJEESH THADATHIL

TO: REID RUTHERFORD WJU BUS670
Date:
Re: OVERVIEW SAAS

Comments: Part 1

SaaS is used to describe a model of software deployment that uses the web to deliver
applications on an “as-needed” basis. All around us, we see companies turning into cutting-
edge, SaaS exclusive powerful corporations, and the reasons for that are pretty self-
explanatory. With more than 80% of their performance app being hosted and maneuvered in
cloud, companies can confidently claim that their operations no longer depend on legacy
systems. This makes absolute sense for all of them, are SaaS benefits often come down to
serious financial savings. The main beneficiaries, as expected, are  small and medium
businesses, which also have the best growth forecasts for 2018.

Businesses are shifting their operations to cloud because:

1. It costs less compared to their legacy systems

2. It cuts their operational costs
3. It enables them to maintain a consistent working process
4. It enables collaboration in large and decentralized teams
5. It saves the time needed for setup and training
6. It facilitates access to data
7. It is mobile-optimized, and independent from the devices they’re using
8. It becomes easier to connect applications with each other
9. It reduces (or eliminates) the burden of upgrading, maintenance, and safeguarding
data
10. It keeps them in line with trends

According to Cisco survey, 83% of the best-performing US businesses planned a SaaS

strategy and considered collaborating with cloud service vendors in 2017. Interestingly
enough, 70% of them had no such intentions in 2016. 2017 was also the year when software
developers understood it made no sense to produce systems that master a single operation, and
not even such that cater to the needs of only one specific industry. Many experts will agree
that the days of vertical software are long gone; to the benefit of do-it-all applications
everybody needs. SaaS is, as they like to put it, neither vertical- nor horizontal-friendly. It is
way better than both, and that’s what makes it successful. Therefore, before you purchase a

1
CLOUD COMPUTING
SaaS system, make sure it is able to integrate with your existing business solutions, and that
you cans also make it work in synergy with homegrown and legacy systems in your company.
Open connectivity is also a bit tricky, so make sure your data will be protected and
safeguarded on several instances.

Part 2

SaaS is used to describe a model of software deployment that uses the web to deliver
applications on an “as-needed” basis. It usually runs on a computer on the Internet, rather than
on the customer’s computer, as is accessed through a web browser. SaaS can be used to reduce
Total Cost of Ownership (TCO) by:
 Spending less money on hardware
 Spending less money on human resources
 Spending less money on software and development

SaaS can increase Return on Investment (ROI) through high-margin multi-tenancy services,
improved ability to create new competitive offerings, and open market opportunities. Example:
 Offering greater financial flexibility
 Offering a wider choice of services
 Increased business agility
 Cost-effective scalability
 High availability with SLAs
 Increased security

When the organization embarks on the strategies, the organization will give the end-users an
opportunity to sign-up and receive services without the long delays. If they consider the broad
network access they will have the ability to access the services via desktops, laptops, mobile,
etc. Having the ability to pool resources together across multiple customers will be a great asset
to the organization. These are just a few examples that will impact the IT support personnel.
Considerations that the organization’s management should be aware of are:
 Understanding Existing Architecture
- Know what IT architecture is already in place
- Know if the company developed the IT architecture from scratch
- Know if the company replaced and exiting architecture
 Assessing Financial Issues
- Quantify costs
- Anticipated life cycles of system components
- Quantify benefits
- Quantify risks
- Consider ongoing dollar costs and benefits
 Assessing Technical Issues: Adaptability

2
CLOUD COMPUTING
- Plan for applications and systems that are independent and loosely coupled rather
than monolithic
- Set clear boundaries between infrastructure components
- Provide access to all users when it makes sense to do so when designing a
network architecture

References

Dr. Paul D. Hamerman and Rackspace Support