SaaS Components is the home of the Salesforce Architect. It was born from the realisation that most of the Salesforce blogs were only targeting two types of professionals:
Because I did not find any blog focused on the important role of the Salesforce architect in implementation teams, I thought I would create one. The content you can find here isn't as technical as the one available in developer blogs, nor is it as feature-focused as admin blogs. There's a bit of both, plus the high-level solution design and delivery perspective that make the role, all based on more than 20 years of experience working on projects of all sizes both on-premise and in the cloud.
In a nutshell, I consider both SaaS and Components to be major concepts of enterprise architecture, and I think that, as a Salesforce architect, so should you. And with this in mind, here is the good news:
- Salesforce is leading the whole SaaS industry
- Lightning is an excellent implementation of enterprise components
The SaaS supremacy
At the end of the nineties, several website hosting companies started diversifying their offers and proposed to their customers to host and manage applications like Microsoft Exchange. They called it the "hosted model". The customer would pay a monthly subscription and wouldn't worry about maintaining the infrastructure.
Then, at the beginning of the millennium, a couple of software vendors also proposed to host their applications in their data centres and named the approach the "on-demand model". If both the "hosted model" and the "on-demand model" offer similar advantages, the latter comes with a massive game changer: the hosting infrastructure is owned and managed by the software vendor themselves...
- The code is now tested on all possible combinations of hardware, file system, VM, OS, drivers, patch, software
- The number of different combination can now be controlled and reduced
- It is possible to release any hot-fix in one batch for all customers worldwide
- The data centre is not a cost centre anymore which prevent budget cuts on tools and people
- Shared capacity planning brings scale savings
- Upgrades are transparent because pre-rehearsed on all the customers' code base
- The vendor can gather usage statistics from the back-end and identify areas of improvement
As you can see the "on-demand model" benefits are biased toward quality, security and resilience: the ideal platform to build an IT landscape on... Around 2005, this architecture got a new name supposed to reflect the nature of the deal: "Software-as-a-Service" (SaaS).
Welcome to my blog!
So, here you go. This explains why I'm a SaaS advocate. Check Why Components? to see why am I a componentization advocate...
I hope you enjoy reading my blog. Don't hesitate to ping me on Twitter if you have any comment or just want to say "hi". Bye for now!