A few years back I wrote a white paper documenting the effort and thoughts that went into building a first generation SaaS platform and subsequent upgrade. While new technologies have been introduced, SaaS is now widely accepted by most companies to deliver their services, and building a SaaS-based application has become increasingly easier, there are some aspects of our original effort that were unique. We developed our first SaaS platform because the traditional web application architecture was inadequate to meet our business objectives. We were in uncharted territory, and customers demanded that we would not mingle their data with other customers' data. So, a common thread in our releases was the isolation of customer data. Many customers today may require the same, for regulatory or privacy concerns, and I thought that by sharing the thoughts that went into designing the first generation SaaS platform and subsequent upgrade would benefit your efforts as well. Our first generation SaaS platform needed some basic components to improve the provisioning and configurability of the application. We needed:
After we launched the first generation platform, over the course of several months we had other important issues to tackle to ensure scalability of platform and scalability of the business processes revolving the operation of the entire SaaS platform. The most significant improvement being the decentralization of the database and ability to use Machine Learning:
Comments are closed.
|
Categories
All
Archives
January 2019
|