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”. Then, 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/controlled by the developers.
- Vendor code can now be tested before release on a known combination of platforms (hardware, OS, drivers, patching level) rather than after release on the thousands of combinations found on customers’ premises.
- It is possible in case of emergency to patch bugs for all customers worldwide in one batch.
- The vendor can gather usage statistics to understand end-users habits and identify areas of improvement.
So, the “on-demand model” offers some clear improvements 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 to customise the software a customer would pay for but also to build new applications from scratch in the Cloud. The industry called this concept “Platform-as-a-Service” (PaaS).
Welcome to my blog!
Everything here is about PaaS in a Salesforce world (force.com).
My posts are mainly aimed at consultants and architects.
You’ll find most of my posts in the “Thoughts” section. I also have some evergreen content which goes in the “Articles” section. And then, I’m storing little bits of code and formula in the section “Snippets“.
I hope you enjoy my blog.