Software as a Service (SaaS) - Design+Code Day; ArabNet Beirut 2015
•Download as PPTX, PDF•
0 likes•426 views
This document discusses considerations for building software as a service (SaaS) applications. It defines SaaS as software delivered over the internet rather than installed locally, allowing users to access applications from anywhere without complex management. The document notes that SaaS revenue was projected to increase 50% from 2012 to 2015, and SaaS growth is expected to be 5 times faster than the software industry overall. Key considerations for building SaaS mentioned are implementing multi-tenancy so one application serves multiple customers, and designing for scaling both vertically by increasing the capacity of individual servers ("scaling up") and horizontally by adding more servers ("scaling out").
Recommended
More Related Content
What's hot
What's hot (18)
Viewers also liked
Viewers also liked (20)
More from ArabNet ME
More from ArabNet ME (20)
Recently uploaded
Recently uploaded (20)
Software as a Service (SaaS) - Design+Code Day; ArabNet Beirut 2015
- 1. Building for SaaS SALMAN AL-ANSARI
- 2. What is SaaS Software as a service (or SaaS) is a way of delivering applications over the Internet—as a service. Instead of installing and maintaining software on-premise, you simply access it via the Internet. Frees the buyer from complex software and hardware management. Still less than two decades old Google, Twitter, Facebook Office 365
- 3. SaaS Revenue Gartner projected more than %50 increase in the revenue $14B $22B 2012 2015
- 4. SaaS Growth According to IDC, SaaS will grow 5 times faster than software industry as a whole x1 Software x5 SaaS
- 5. SaaS vs On-Premise Revenue Model Upgrades Infrastructure
- 7. Considerations for Building SaaS Multi-Tenancy Scaling
- 9. Scaling Scaling Up Scaling Out
Editor's Notes
- Compared to $14B in revenue in 2012, Gartner predicts that the revenue will grow to around $22B in 2015
- Revenue Model: SaaS software billing is usually based on the concept of subscription where buyer is billed monthly or annually in return of software service where in on-premise software it is usually licensed one down payment, with annual support for example. Upgrades: SaaS providers upgrade the solution and it becomes available for their customers. Costs and effort associated with upgrades and new releases are lower than the traditional model that usually forces the user to buy an upgrade package and install it, or pay for specialized services to get the environment upgraded Infrastructure: software on-premise is installed on buyer infrastructure. All scaling and physical servers with redundancies is kept at the customer’s location. Where SaaS is installed on the providers hardware on the cloud and thus the provider has to consider about customer’s data security and application scaling…
- Multi-tenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple tenants. Each customer is called a tenant. Tenants may be given the ability to customize some parts of the application, such as color of the user interface (UI) or business rules, but they cannot customize the application's code. Also, competitors may not want their data to reside at the same location which enforces data isolation. This is an example of a multi-tenant architecture in three tiers system. Each tenant is given a separate UI and the differentiation is done using different subdomains. All customers may use a shared web server and then again a multi-tenant database where each customer data is isolated from others. This is just like in an apartment building—in which many tenants cost-efficiently share the common infrastructure of the building but have walls and doors that give them privacy from other tenants. This results in a lower cost since multi-tenant SaaS applications are serving different customers with a shared single instance instead of an instance for each customer.
- To scale vertically (or scale up) means to add resources to a single node in a system, typically involving the addition of CPUs or memory to a single computer. To scale horizontally (or scale out) means to add more nodes to a system, such as adding a new computer to a distributed software application. There are tradeoffs between the two models. Larger numbers of computers in scaling out means increased management complexity, as well as a more complex programming model and issues such as throughput and latency between nodes. However, scaling up has a greater risk of hardware failure causing bigger outages. Moreover, scaling horizontally (scaling out) is usually cheaper overall and can literally scale infinitely .