PaaS in a Salesforce world.
At the end of the nineties several website hosting companies started diversifying their offers and proposed their customers to host and manage applications like Microsoft Exchange. This was called the “hosted model”. At the beginning of the millennium, some software vendors also proposed to host their applications on their own infrastructure. This was called the “on-demand model” but was often confused with the “hosted model”. If both models offer similar advantages like the often mentioned “move from Capex to Opex” and both pros and cons of outsourcing, the “on-demand model” comes with a game changers: the hosting infrastructure is owned by the developers.
- Code is tested on all possible server combinations (hardware, OS, drivers, patching level).
- It is possible to release any hot-fix in one batch for all end-users worldwide.
- The vendor can gather, from the back-end, usage statistics to identify UX issues.
As you can see the “on-demand model” offers some clear advantages in terms of software quality.
Around 2005, this architecture got a new name supposed to reflect the nature of the deal: “Software-as-a-Service” (SaaS). When maturing SaaS become such a powerful platform that it enabled not only basic customisation but also new applications development. The industry called this new concept “Platform-as-a-Service” (PaaS).
Welcome to my blog!
Everything here is about PaaS in a Salesforce world (force.com) with posts mainly aimed at consultants and architects.
I hope you enjoy reading.