We are planning to build a site from scratch on Sitecore 8.2 update 1 and are struggling to decide between Azure PaaS and IaaS.

While we are excited about PaaS, we feel organization wise, we are not ready to dive into PaaS just yet.

Assuming there is an opportunity to move to PaaS in future, is the path to developing Sitecore sites same for both IaaS and PaaS?

How easy or difficult would it be to move an existing site written in 8.2 update 1 non-Azure to Azure PaaS?

Any architecture guidelines we need to follow so that future PaaS migration is possible?

  • I agree with Richard. As someone who regularly talks to CxO level to get by into moves to cloud, senior management need to be taken along on the journey. Understanding of PaaS v IaaS is also patchy at times. There needs to be the investment by the senior team to understand the key characteristics and why PaaS is a good move. There are a few limitations you should be aware of 8.2.1.see thread: sitecore.stackexchange.com/questions/4308/…
    – Dan Berry
    Commented Feb 21, 2017 at 14:52

1 Answer 1


Saying "I'm not ready for PaaS" is like saying "I'm not ready to get my electricity from a hole in the wall, we want to see all the Tesla coils actually generating the electricity so we can be sure it's real electricity. We need to control how often the coils are cleaned."

Azure PaaS is just IIS without all the Windows bits accessible. If you're making a website, why do you care about the O/S hosting the web server? The world has been using PaaS web servers in the form of cPanel for an eon from every small hosting shop anywhere. This is not cutting edge stuff.

The good news is that you can build your site with almost no consideration for PaaS or Iaas (remember PaaS is just someone else's computer) as they are really just both IIS in the end. There are a few platform considerations you need to make if you plan to scale your environment, though. When you need to go to 2 instances, you need to treat it like 2 servers behind a load balancer with a shared file system (can you guess why? 'cause that's what it is). In this setup Solr is better than Lucene, Redis/Mongo session is better than InProc.

The remaining considerations (like the Sitecore "data" folder handling) should be managed through the platform itself. I haven't had a close look at 8.2.1 yet but I'm reliably informed the last few bit that caused complications have been re-engineered to cope properly. Either way, adding the {COMPUTERNAME} into file system paths will usually suffice to keep instances from tripping over each other.

I'd suggest running your CM on a single instance though, unless you have very heavy publishing needs.

Don't forget that you can attach a debugger to a PaaS IIS just like you can with a VM. What else does the VM really give you that you can't give up? There's so many good reasons to go Paas:

  • Automatic backups
  • Multiple deployment slots
  • Fast scaling
  • No more Windows updates
  • No O/S "hardening"
  • Minimal attack surface
  • No more infrastructure to configure and maintain
    • NICs
    • Firewalls / Network security groups
    • Virtual networks
    • Disks & disk space management
    • Swap space
    • Memory management

What's not to like?

  • While I do agree with all the rational described in moving towards PaaS, in large organizations such as ours, we would need blessings from upper management which could end up in delays and potentially missing the project deadline.
    – xoail
    Commented Dec 10, 2016 at 17:17
  • 2
    I would expect upper management to be involved in decisions like these in all sizes of organisation. But as you can see - there's an easy case to make here. What holds most companies back is uncertainty over the price. This is quite a well-founded rationale, and costs can escalate if not managed carefully. None of this is free, after all. In aid of your question though, there's little consideration you need to make aside from designing your solution for "scale-out". Commented Dec 10, 2016 at 22:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.