The publishing service is designed with “the cloud” support in mind, including is the ability to deploy the publishing component itself as a an application service which can bring many benefits to customers such as:
- Cheaper to run compared to VMs. As the new publishing service is so efficient in using CPU and memory. A cheap B1 basic tier would be sufficient to host the service.
- Zero-configuration/out of the box high availability setup, this can be achieved by scaling out the environment using Azure portal. This feature will be covered in details in another post.
Before diving into the details, it’s worth mentioning that the publishing service can be deployed on the same CM server or even on the DB server as IIS website. The closer to the source db the better. However, this post will make more sense if you want to free some load from the CM server or to provide resiliency and avoiding single point of failure scenarios.
The following steps will talk you through the process of installing the publishing service on azure and configuring it to connect to your existing Sitecore database.