Terrosa Technologies SaaS Blog

Just another WordPress.com weblog

Archive for December, 2008

Thinking about SaaS: The goal of more efficient software

Posted by terrosatechnologies on December 6, 2008

This Thinking about SaaS focuses on why SaaS is truly a better answer for delivery of software. We are not just talking browser based applications, but why properly architected SaaS software applications have a true efficiency advantage over locally installed systems. For you, the software user or the software provider, understanding these architectural differences will at some point benefit your bottom line.

 

To understand the subject of software efficiency, consider how we arrived at this point. I will use financial accounting as an example. Many years ago, all software was built in-house. There were no packaged financial applications. Big companies, using big systems, each built their own accounting systems. Over and over and over this process was repeated, with the help of programmers from IBM and others. Each end user company duplicated efforts, with an attempt to make the process more efficient through better coding practices.

 

Then financials in the form of a set of pre-written base code arrived from the vendors. This code base was a starting point from which each company customized and re-worked to meet their specific needs. Companies could start with this generic set of code, rather than starting from scratch.

 

Further attempts to make application development more efficient all stemmed around reducing the amount of coding needed to produce an application. Re-usable code, object oriented programming, high level application development tools, etc.

 

What eventually won out were packaged financial applications. Generic software packages became so full featured, with so many options, that most companies no longer needed to write their own financial software.

 

What is still very inefficient about this approach is on the operational side i.e. the repetitive nature of each customer installing, upgrading, fixing, patching, and maintaining these applications. Also, each individual customer is free to choose different hardware, operating systems, databases and upgrade schedules. This forces software vendors to support multiple releases, multiple versions of their product, and deal with all sort of issues because of these platform inconsistencies.

 

Outsourcing companies known as Application Service Providers, attempted to improve these software affecting platform inefficiencies by offering services to run applications for companies offsite. Citing operating efficiencies, hardware standardization, consolidation of support personnel and other reasons; companies such as IBM, EDS, HP expected to run applications for less money than companies could run them internally. The fundamental problem with this approach is that the ASPs, were still supporting software that was designed to be used by only one company. So while in a centralized location, ASPs were still installing, upgrading, fixing, patching and maintaining many copies of the application and customers were still dictating upgrade schedules and customized features.

 

 In a true SaaS environment, the software provider chooses to run their application on a consistent set of equipment with one operating system, one database, supporting one current release. The entire customer base is running in this consistent environment. Support is unnecessary for back releases, various types of databases, multiple operating systems and different hardware brands. This scenario is only made possible by a multi-tenant software architecture.

 

So what this history lesson clarifies for us now, is the fundamental driver behind SaaS efficiency – a ground up multi-tenant design that allows application sharing across many organizations.

 

Be aware that terminology in the SaaS world is ‘clouded’ by vendors whose marketing department may be a few years ahead of their software teams, calling their products SaaS when they don’t have this multi-tenant design. Vendors in this situation may still have the inefficiencies of the ASPs behind the scenes while calling themselves SaaS vendors in their written materials.   

 

As true multi-tenant SaaS software matures, with the ability to support more and more complex business needs, with all the operating benefits of multi-tenant operations, it is clear that SaaS is truly a fundamental shift in how software is used.

 

  

______________________________________________________________________

 

This “Thinking About SaaS” article is one in a series produced by Terrosa Technologies’ President, Kim A. Terry. Each article addresses a different knowledge area of applications delivered via the SaaS subscription model.

______________________________________________________________________

 

 

About Terrosa:

Terrosa Technologies was born out of the recognition that software provided as a service produces greater efficiency, value and benefits over traditional site installed solutions. Enabled by a fast reliable Internet and the ever increasing sophistication of Saas offerings, many companies will be able to reduce their cost of operations and afford to do more with less. In uncertain and financially challenging times, it is more important than ever that Terrosa is helping our customers deliver products and services more efficiently and with less risk.

Posted in SaaS, Software as a Service, Uncategorized | Tagged: , | Leave a Comment »

SaaS – Infrastructure Efficiencies

Posted by terrosatechnologies on December 5, 2008

This Thinking about SaaS focuses on how infrastructure savings are derived from the efficiencies gained through the SaaS delivery model, which in turn drive down the total cost of using software.

 

It is clear that Software as a Service is a “Disruptive Technology”, shifting infrastructure and its operation from end user companies to centralized datacenters run by platform providers.

 

Substituting an individual company’s internal infrastructure with a SaaS based solution should be easy to quantify. Calculating internal amortized hardware/software acquisition costs + operating costs vs. Saas subscription fees gives an organization a clear picture on the financial justification.

 

But there is a broader argument that SaaS delivered solutions have such an efficiency advantage when compared to onsite solutions, consuming software any other way cannot be justified on cost alone. As SaaS becomes a larger percentage of the software market, the financial advantages become even more pronounced.

 

Take a traditional site installed application that has a web interface and a database. This application requires a minimum of 3 servers to run – 1 database server, 1 application server and 1 web server. This scenario has no clustering of servers for redundancy, offsite disaster recovery or other reliability measures, but is simply the minimum configuration.

 

Over time, the software provider sells their software package through traditional channels to 800 customers. Each of these customers purchase, install and maintain 3 servers for a total of 2400 servers across the entire customer base.

 

Each customer also consumes about ¼ of a person a year to maintain the environment, apply patches, and to install new releases of the application every 6 months. This totals 200 FTE resources employed to support the software package across the entire customer base of the software provider.

 

Now take the same software package, but the software provider sells their product as a service to the same based of 800 companies. They build two highly redundant, high capacity installations, in high security data centers, in two different states. This takes approximately 50 servers per location, storage area networks, data replication tools, etc.

 

They also need highly qualified operations personnel to run 24/7. 1 Director, 3 Managers (1 each shift), 5 DBAs, 2 network engineers, 3 server engineers, and 6 first line help desk people. This totals 20 people to operate the system.

  

So let’s recap:

 

2400 servers for site installed, 100 servers needed for the SaaS scenario

200 people needed for site installed, 20 people needed for the SaaS scenario

 

Also, note that the SaaS scenario has full redundancy both within a site and across sites in two different states, with live staff 24/7.

 

Similar figures apply to power, air, floor space and other datacenter requirements.

So, the case for SaaS is obvious from a ‘Green’ perspective, as well.

 

This big picture view clearly shows how the efficiencies of SaaS application delivery will drive down the cost of IT infrastructure for everyone as more adoption occurs and technology costs are spread across multiple organizations.

  

______________________________________________________________________

 

This “Thinking About SaaS” article is one in a series produced by Terrosa Technologies’ President, Kim A. Terry. Each article addresses a different knowledge area of applications delivered via the SaaS subscription model.

______________________________________________________________________

 

 About Terrosa:

Terrosa Technologies was born out of the recognition that software provided as a service produces greater efficiency, value and benefits over traditional site installed solutions. Enabled by a fast reliable Internet and the ever increasing sophistication of Saas offerings, many companies will be able to reduce their cost of operations and afford to do more with less. In uncertain and financially challenging times, it is more important than ever that Terrosa is helping our customers deliver products and services more efficiently and with less risk.

Posted in SaaS, Software as a Service | Tagged: , | Leave a Comment »

Thinking about SaaS

Posted by terrosatechnologies on December 5, 2008

Thinking about SaaS is a blog about various SaaS related topics important to organizations and software providers looking to make the move to utilize Software as a Service.

Posted in SaaS, Software as a Service, Uncategorized | Tagged: , | Leave a Comment »