Hello Rajinder

I'd recommend reading this artcile Azure: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-CMS/75/Deployment/Deployment-scenarios/Deploying-to-Azure-websites/

Also the following for AWS: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-CMS/75/Deployment/Deployment-scenarios/Deploying-to-Amazon/

The ServiceBus queues are used to allowed Azure WebApp instances to send events between each other. This is primarily used to send cache invalidation messages to ensure cache's are kept in sync when load balancing.

Personaly I'd used PAAS if setting up a new environment, as management is easier when elastic scaling and it could work out cheaper than IAAS.

David

David,

Thanks for taking the time to repond. I have read the links you referenced above along with anything else I found on the web about EPIServer deployed on public cloud.

I completely agree with you that PAAS will be easier to manage and be probably cheaper.

Documentation clearly states that EPIServer supports PAAS.

We are helping a customer which had deployed EPIServer on Azure. They are currently using IAAS. They had deployed EPIServer on IAAS because the partner that deployed EPIServer was not comfortable with PAAS. At that time EPIServer might not have been supported on Azure PAAS.

We specialize in Public Cloud and DevOps so I will try to create templates that can be used to quickly setup scalable EPIServer environments in Azure and AWS.

Raj

Depending on your project characteristics and behavior you may be forced to stick with IaaS (for instance if project was not intially design to be hosted in cloud, accessing network share for some import/export comes first in mind). But other than that - we have successfully deployed IaaS and PaaS solutions (even Commerce as PaaS) to the cloud and personally I prefer PaaS and lot of headaches for managing infrastrucuture just goes away.