On-premise

On-premise servers were one of the earliest paradigms, where the companies producing software had to not only deal with designing, architecting, and writing the code, but also had to execute and create a rainbow of auxiliary activities and elements, as follows:

• Budgeting, purchasing, and arranging for real estate to host servers
• Budgeting and purchasing of bare metal computational and networking hardware
• Installation of computational assets
• Equilibrium of environment
• Authoring code
• Configuration and provisioning of servers
• Deployment strategies
• Designing and implementing strategies for  high availability of the applications.
• Backup and restore mechanisms
• Performance and scalability
• Patch management and uptime

The typical makeup of such a company had a less-than-optimal ratio of the development team to the overall headcount, vastly slowing down the delivery of its most valuable proposition, which was designing and shipping software.

It is obvious, looking at the scope of the preceding work, that such a setup and work environment posed a lot of hurdles to the growth of the organizations, and had a direct impact on their bottom-line.