Guide to Private SaaS Applications
Software as a Service (“SaaS”) has brought about a revolution in the way software is delivered to customers. The SaaS model evolved to alleviate the difficulty of adoption, large upfront investment and high cost of maintenance that traditional on-premise software required of customers. It has largely succeeded in these objectives by using subscription pricing and shifting the hardware procurement and software operational burden to the vendor. According to IDC Research, Cloud software, an approximation for SaaS, will grow to $112.8 billion by 2019 at a compound annual growth rate of 18.3%.
However, these benefits do come with some trade-offs to the customer, including less data control, resource sharing with other customers and limited integrations across SaaS applications. In addition, there are still many workloads that need to be on private infrastructure due to regulation, latency, existing capital investments or other reasons.
“Cloud software will grow to $112.8 billion by 2019 at a compound annual growth rate of 18.3%.”
Private SaaS is a software delivery model that combines the benefits of SaaS and on-premise models. It does so by the software vendor continuing to provide many of the “services” required to run the software but deploying the software on the customers’ private infrastructure so the customer has more control over their data and the environment in which the application runs. This is not an entirely new concept but with the broad adoption of next- generation container technology, like Docker and Rkt and container orchestration systems, like Kubernetes and Mesos, this model is now easier and cheaper to deliver than it has been in the past.
In this paper we will discuss the technical details behind the platform we have developed to deliver Private SaaS, called Telekube.