SaaS Architecture Guidance on

Some of the content we have been working on, is now available on You’ll find a video (18min.) introducing some of the SaaS architecture issues, a PowerPoint presentation I gave at several architect forums and a link to our overview whitepaper.

More to come soon, enjoy!

Comments (3)

  1. [Daily Post from Cesura] Business Certainty: Business Certainty: SaaS for any Size Company: XS, S, M, L "Perhaps it would be easier to start focusing on where SaaS hasn’t quite caught on yet than chronicling everywhere that it has. And…

  2. tomgross says:

    Gianpolo, your session at TechEd was my first exposure to your group, great to see that Microsoft finally has an SaaS champion!  As VP of R&D at a Microsoft based SaaS ISV, I’m quite familiar with many of the issues that you discuss in your whitepaper.  I’m somewhat confused though with your level IV Maturity model, and specifically the part that states "with each customer’s data kept seperate."  This seems to contradict the whole multi-tenant concept, and it doesn’t mesh with the Data Scaling section later in the whitepaper either.  It’s probably just a semantics issue, but I’d appreciate if you could clarify.

  3. gianpaolo says:

    Hi Tom, level IV describes a level where multiple instances are introduced to cope with scale. A pure single instance architecture (level 3) can only scale up (obviously, as you have only 1 instance of DB). By introducing data partitioning techniques (e.g. partitioning by tenant ID) one can scale out (instead of up) the SaaS application.

    There are 2  points here:

    – differentiate scale up from scale out architectures

    -differentiate multiple instances for scale reasons vs. multiple instances due to non multi tenant architecture (level II)

    I hope this clarifies the model, if not my email is gianpc@….. (you know the company)

Skip to main content