Software As A Service (Saas)
Software As A Service (Saas)
(SaaS)
Does it make Cents?
by
Brian Moore
Contents
Brief Background information
SaaS Architecture
Financial Consideration
Case Study
Conclusion
Q&A
Intro to SaaS - Definition
Software as a service (SaaS) is a model
of software delivery where the software
company provides maintenance, daily
technical operation, and support for the
software provided to their client.
It assumes the software is delivered over
the internet.
Software delivered to home consumers,
small business, medium and large business
Intro to SaaS
The web as a platform is the center point
Web-browser acting as a thin-client for accessing
the software remotely across the internet.
Network-based access to, and management of,
commercially available (i.e., not custom) software
application delivery that typically is closer to a one-
to-many model (single instance, multi-tenant
architecture) than to a one-to-one model, including
architecture, pricing, partnering, and management
characteristics
SaaS - Pros
Stay focused on business processes
Change software to an Operating Expense instead of a
Capital Purchase, making better accounting and budgeting
sense.
Create a consistent application environment for all users
No concerns for cross platform support
Easy Access
Reduced piracy of your software
Lower Cost
For an affordable monthly subscription
Implementation fees are significantly lower
Continuous Technology Enhancements
SaaS - Cons
Initial time needed for licensing and
agreements
Trust, or the lack thereof, is the number one
factor blocking the adoption of software as a
service (SaaS).
Centralized control
Possible erosion of customer privacy
Absence of disconnected use
SaaS Architecture
Fueled by
Bandwidth technologies
The cost of a PC has been reduced significantly
with more powerful computing but the cost of
application software has not followed
Timely and expensive setup and maintenance
costs
Licensing issues for business are contributing
significantly to the use of illegal software and
piracy.
High-Level Architecture
There are three key differentiators that separate a well-
designed SaaS application from a poorly designed one
scalable
multi-tenant-efficient
configurable
Scaling the application - maximizing
concurrency, and using application resources
more efficiently
i.e. optimizing locking duration, statelessness, sharing
pooled resources such as threads and network
connections, caching reference data, and partitioning
large databases.
High-Level Architecture (con’t)
Multi-tenancy – important architectural
shift from designing isolated, single-tenant
applications
One application instance must be able to
accommodate users from multiple other companies at
the same time
All transparent to any of the users.
This requires an architecture that maximizes the
sharing of resources across tenants
is still able to differentiate data belonging to different
customers.
High-Level Architecture (con’t)
Configurable - a single application instance on a
single server has to accommodate users from
several different companies at once
To customize the application for one customer will
change the application for other customers as well.
Traditionally customizing an application would mean
code changes
Each customer uses metadata to configure the way
the application appears and behaves for its users.
Customers configuring applications must be simple
and easy without incurring extra development or
operation costs
Saas Financials
4 ways software companies are pricing their products
Open Source – free basic products but charge a fee for