title: Dedicated Sitecore CM publishing instance in a load balanced environment
body: <p>We need to setup a load balanced CM environment for Sitecore - mainly for failover purposes, but also for times when the load might get too heavy. We are going to have two servers for this. I was going through the scaling guide, and they mention that in a load balanced CM environment, it is necessary to have one server dedicated to publishing. The remark states that it is mainly for performance, but I've heard people state that unless you setup the dedicated publishing instance, the publishing queues doesn't get synchronized. I guess I understand this, based on how the sitecore publishing queue works, but what is the point of having a load balanced CM environment if there is a dependency on one of the servers? Granted its not a 'site down' dependency, but its a dependency none the less - is there a way around this?</p>
  
  <p><strong>Edit</strong></p>
  
  <p>I have a few answers here that all point to the fact that it may be a performance issue or a deadlock issue, so I guess my real question is, how do you make a failover for the dedicated publishing instance, because now a singular publishing instance will become a central point of failure.</p>