Iâ€™m in the early stages of writing my thesis about SaaS. As
part of this process Iâ€™m reading loads of SaaS content. Mainly, Iâ€™m monitoring Gianpaolo Carraro and Fred Chong blogs (from
the Microsoft Architect Strategy group) and a weekly SaaS newsletter.
in its infancy in terms of guidance and realization and as a result, my
thesis outline consists of analyzing the state of the art and fulfills the architectural
concepts by writing a reference implementation of Software as a Service using
Microsoft technologies (WinFx, ASP.Net 2, etc.).
Fred and Gianpaolo wrote a great paper that has been
published on MSDN about architectural
strategies for SaaS.
The paper starts by talking about the business value proposition of SaaS. Leveraging
economy of scale and selling for the long tail are really attractive concepts.
The other half of the paper examines architectural implications
when adopting this model: the SaaS maturity level, metadata services,
multi-tenant and scale out among other things.
This paper is a first approach on the subject and it introduces
concepts like Metadata Services which I found one of the key challenges
to fulfill in terms of guidance because it is a cross-cutting concern in SaaS
The following is my first approach on how I would like to achieve
Metadata Services using the Microsoft stack.
I would like to make a special comment on â€œExtensions to
the data modelâ€. In the previous months we, at Southworks, customized extensively the
process template of VSTS
to fit our needs. This customization has been really straightforward and it
allowed tailoring our specific requirements not only for our SDLC but also on
other business processes. That proved us that XML succeeded as a metadata
language. The guys from VSTS did a great job by providing these metadata
services and I would like to explore more the intrinsic of it.