Software as a Service

Article Info

Contributed by
2 authors

Last updated on
2022-03-05 11:27:29

Migrating to SaaS
SaaS Architecture
Serverless Architecture
Cloud Native Computing
Cloud Architectural Design Patterns
Cloud Security

Article Versions

16 2022-03-05 11:27:29
3507,3506 16,3507

By arvindpdmn

Implementing remaining review comments. Publishing but milestones section requires lot of improvement.
15 2022-03-05 10:33:42
3506,3504 15,3506

By arvindpdmn

Correcting ref and citation formatting.
14 2022-03-05 05:39:59
3504,3501 14,3504

By arvindpdmn

Updating See Also based on scope of identified topics. SaaS arch is potentially a separate article.
13 2022-03-03 21:10:44
3501,3496 13,3501

By Govindpathak

Implemented suggestions given in review.
12 2022-03-02 10:29:51
3496,3491 12,3496

By arvindpdmn

Rewording content in Summary. One ref formatted with correct details.

Chat Room

Submitting ...

You are editing an existing chat message.
2022-03-05 09:23:55
-

By arvindpdmn

I am editing the article for comments not implemented. Hope to publish today.
2022-03-03 21:14:18
-

By Govindpathak

Performed all the changes, revisions & additions. Please have a review.
2022-03-02 11:13:26
-

By arvindpdmn

1. The figure highlights hidden costs: text has some explanation but link it to the term "hidden costs".
2. Architecture image is missing. For an article on SaaS, this is important. In general, images are lacking in the article. Images make it easy for readers to understand. Architecture answer is poor. Explanation needs to be deeper.
3. Characteristics:
- TCO: no hidden cost: this is the main explanation. It could have been explained in fewer words.
- "Unlike the on-premises software" or similar phrases: don't overuse this. It's okay to say this once in the Summary and once more elsewhere.
- Data security: poorly explained.
- Scalability: no-cost & easy installation: not clear. These are not the main reasons. Nothing is no cost: everything is billed.
- Subscription fee: okay but should also mention savin
4. I noticed that you didn't change "Open SaaS" to "OpenSaaS". Any reason? It also looks like one of them is a trademark. Investigate more. Which should be use?
5. Vertical vs horizontal:
- Image is very textual: this doesn't add value. It definitely gives more information. Anyway can keep the image for now until we find a better on.
- Image attribution is incomplete: say table 2, fig. 3.2, etc. See other published articles for example.
- "Salesforce(CRM)" change to "Salesforce (CRM)". In general, put space before parenthesis. Correct in other places as well.
6. "build a SaaS product": can you make it more developer relevant? Answer relies on only one source. Never a good idea.
7. Milestones could be better. Anyway, you have three, so that's fine for now.
8. Refs
- Some journals are not good sources: Sahoo et al. paper is an example. Alotaibi paper is also not good but paper is well written, so allowing it.
- Replace three cloudfront URLs with alternative URLs for the same refs. In fact, these refs don't have sufficient details. Just saying Acamedia is hardly enough. If unable to find, find alternative refs.
- "JOURNAL OF DIGITAL ASSET MANAGEMENT.": don't capitalize this way.
- Dates missing in some refs. Kazmi is an example.
- Author's name is "Dan Ma". Therefore, change MA to Ma.
- Jain and Jain is wrong: ref has three authors: it should be Jain et al. 2010. Study Author Guidelines and examples from published articles.
- Turner: three authors not formatted correctly: Study Author Guidelines and examples from published articles. Or use the ref formatting tool until you learn this stuff.
2022-02-28 18:03:22
-

By Govindpathak

Article is ready for the review.
2022-02-28 18:02:31
-

By Govindpathak

Implemented all the changes & improvements suggested in the review.

11. I tried to find every possible question from all the references. Some of them were out of context for this article as it is for developers specifically.

Software-as-a-Service (SaaS) is a software delivery model that allows multiple users to use a software hosted on a cloud server. It has replaced the traditional model of software installation on on-premise servers and desktop computers.

SaaS leads to rapid deployment, better user adoption, reduced support needs and less maintenance overheads. Customer support is also faster and more efficient than traditional on-premise software. Salesforce, Dropbox, Cisco and Webex are some famous examples of SaaS providers.

While adoption of SaaS solutions has been exponential, there are still some organizations reluctant to adopt SaaS mainly due to the risk of data security and limited customization.

Discussion

What's the reason of exponential growth of SAAS?
Hidden costs in traditional software model. Source: Waters 2005, fig. 2.
SAAS has replaced the traditional on-premises software which needed to be installed at organizations. On-premise software have many hidden costs in terms installation, maintenance, personnel training or even downtime. SAAS has eliminated the hardware installation & maintenance cost of software. It allows the users to only focus on their dedicated services without thinking about availability, speed or maintenance of the software. Also, it is very easier to use than traditional on-premises software.
In SaaS deployment models, software vendors are responsible for the reliability of the software delivery platform, IT infrastructure, software development, hardware maintenance, security, user support and data backup. The consumer can be assured of the reliability of the hosted software service through a contract called a service level agreement (SLA).
SaaS proved to be a profitable model for both consumers & software vendors. While consumers could avoid the overhead of maintenance & in-house IT resources, vendors could have more economic benefits in software production and distribution and a shorter product development lifecycle.
Due to these competitive advantages over traditional software SaaS grew exponentially over the years.
What are some famous examples of SaaS?
There are multiple examples of SaaS based companies, that not only affect our day-to-day lives but also generate millions of dollars in revenue. Some famous examples of SaaS are as following-
Salesforce: It is a cloud-based CRM (Customer Relationship Management) used to boost the sales of organizations by managing all the leads and prospects at one place.It is one of the oldest & most esteemed examples of SaaS. It was launched in the year 1999. It generates a revenue of 13.28 billion USD.
Dropbox: It is a cloud-based file storage platform used to store and access files worldwide. It's one of the reputed startups of USA. It was launched in the year 2007 & generates a revenue of 1.6 billion USD.
Google Applications (G suite): Google provides a bunch of SaaS applications inside G suite such as Gmail, Google Docs, Google Sheets, Google Drive & many more which makes our daily professional life very easy & convenient. It was launched in the year 2006 & generates a revenue of 2.6 billion USD.
What are different types of SaaS architectures?
Difference between single tenant & multi-tenant architecture. Source: Glib 2021
Different types of SaaS architectures as following -
Monolithic Architecture: The monolithic SaaS software is an indivisible module consisting a big database & a solution that is built around a server-side and client-side interface. All the functions are managed and served at one location.
Microservices Architecture: In this architecture, each function of the SaaS product is an independent module that can be deployed separately as required. Application Programming Interfaces (APIs) enable modules to communicate with each other and sync their independent processes to work as one single entity. Each service can be upgraded, updated, and scaled separately.
Single-tenant Architecture: This architecture serves a dedicated client. Dedicated software instance, infrastructure & database is given to the client.
Multi Tenant Architecture: Unlike single tenant architecture, multi-tenant architecture allows sharing resources. Each tenant's data is secured and protected.
What does it take to build a SaaS product?
Below are the steps to create a SaaS product-
Analyze the market: The prior step is to analyze the market. Questions such as who is the target customer?, who are the competitors?, what is the problem that the product will solve? should be asked.
Develop a business & marketing plan: Plan for making the SaaS product unique, profitable & successful in solving the targeted problem.
Define SaaS requirements There are many common characteristics of SaaS solutions such as multi-tenancy, optimized solution and data security . Decide the features & functionalities of the product.
Choose the technical stack: The technology stack is list of programming languages, frameworks and tools used to develop the software. Decide the preferred technologies for front-end, back-end & database of the SaaS product.
Choose the SaaS hosting provider: There are many SaaS hosting providers such as Amazon (AWS), Google, Microsoft, Heroku and many more. Choose any of them to host the software.
Create the team: For the success of the SaaS product, a team of experts in different fields such as marketing & designing should be made. One can also hire a software development company for developing the software.
What are some important characteristics of SaaS?
Following are some important characteristics of a SaaS product-
Total cost of ownership (TCO): There are no hidden costs in SaaS.
Data Security: Data security is an important aspect of any SaaS product. Due to multiple users, it's important to encrypt the data of each user.
Scalability: Resources are allocated/released dynamically to serve immediate performance requirements. SaaS can scale vertically (more powerful resources) or horizontally (more resource instances).
Multi-tenant: Multi-tenant is a method in which a single software hosted on a remote server, serves multiple clients(tenants). Muti-tenancy allows faster updates deployment.
Personalised Customization: Unlike the on-premises software, users can customize the software accordingly at both UI level & software business logic level.
Optimized utilization Customers can purchase exactly the requirements(data storage, bandwidth, software features) & can extend it whenever they want.
Subscription fee: The consumers pay a monthly/annually fee to use the software. Hence, they save the costs of software installation, maintenance & upgradation.
Reliability: The requirements of businesses to run 24/7 is fulfilled efficiently with SaaS. Many vendors mention the reliability promise as an integral part of their contract, guarranting an uptime of upto 99.5 per cent.
What is Open SaaS?
Open SaaS is a form of SaaS that is built on open-source code. Such software are initially developed by an individual or organization but later used & improved by many developers. OpenStack, OpenNebula, Cloudify, Wordpress, OpenShift and CloudStack are good examples of Open SaaS.
Major upgrades & product updates are controlled by the central provider whereas the community of users also contribute to the development of the software.
Whereas Wordpress is developed by the company Automattic, it is completely open source, in terms of both licensing & practical usage. Automattic never charged a penny to the thousands of Wordpress-based website owners while many developers who contributed in making continous improvements in WordPress code base and plug-ins never received a dollar for it.
What's the difference between vertical & horizontal SAAS?
Differences between vertical and horizontal SaaS. Source: Bhattacharya 2020.
Horizontal SaaS is a type of SaaS that targets a wider network of businesses, regardless of their industry. Examples of Horizontal SaaS are QuickBooks (accounting) and Salesforce (CRM). Horizontal SaaS is more familiar than Vertical SaaS. Due to targeting a wider market, Horizontal SaaS business owners manage to acquire the customers at a lower cost.
Whereas, Vertical SaaS software are made for a specific niche industry. BioIQ(MedTech) & Health Assurance Plan(dental software) are examples of Vertical SaaS software. Due to a industry specific solution, the size of potential market for Vertical SaaS owners is lower. Vertical SaaS solutions are often made by the experts of a certain industry.
What can be the challenges of adopting SaaS?
Consumers can face some challenges in adopting SaaS. Adopting SaaS model involves risks in terms of data recovery and migration, high switching costs, lack of software customization features and integration with software. There is a risk of losing important data for consumers while migrating the data from one SaaS vendor to another. Service suspension due to lack or delay of payment can also cause data loss. Customers may find it hard to customize features with SaaS. The critical & important data of enterprises should also be kept hidden to other users of the service. Availability of the services is also a big concern. The disruption of the Amazon cloud service in the year 2011, took down a number of websites including Reddit, Foursquare, and Quora. SaaS works on a muti-tenancy model in which data of different users reside at the same location. Intrusion of data of one user by another becomes possible in this environment.
Weak cloud standards can also resist enterprises from adopting SAAS. SAS 70 Audit is a common cloud standard. ISO 27001 is a better cloud standard than SAS 70 Audit.

Milestones

1999

Salesforce, a company based on the complete SaaS software is released. It serves the purpose of Customer Relationship Management (CRM).

2006

Amazon introduces Amazon Web Services(AWS), providing on-demand cloud computing platforms and APIs to individuals, companies, and governments. Now, developing & hosting the SaaS software becomes easy for SaaS developers.

2020

The market size of SaaS reaches to 157 billion US dollars.

References

Article Stats

1543

Words

Authors

Edits

Chats

Likes

1610

Hits

Cite As

Devopedia. 2022. "Software as a Service." Version 16, March 5. Accessed 2023-11-13. https://devopedia.org/software-as-a-service

Contributed by
2 authors

Last updated on
2022-03-05 11:27:29

tools devops architecture

Migrating to SaaS
SaaS Architecture
Serverless Architecture
Cloud Native Computing
Cloud Architectural Design Patterns
Cloud Security

Software as a Service

Discussion

Milestones

References

Further Reading

Article Stats

Author-wise Stats for Article Edits

Cite As

See Also

Login