title: NServiceBus, WCF Architecture
body: <p>So I'm looking into implementing NServiceBus in our current setup and just trying to get a better understanding of how things should be setup.</p>
  
  <p>Our current setup consists of multiple clients (websites, scheduled tasks, etc..) calling a WCF service we have set up for handling the sending of emails. Of course, if the service goes down then our clients start getting errors and all of those messages are then lost (one of the reasons we want an ESB). </p>
  
  <p>I've seen how you can configure your WCF service to handle nservicebus messages in a pub/sub setup. What I'm not sure on is what is the best way to set it up.</p>
  
  <p>Setup 1:</p>
  
  <p>Client (Publisher) -> NServiceBus handler (Subscriber) -> WCF Service</p>
  
  <p>In this case, to scale you'd increase the number of handlers (hosted nservicebus services?), keeping just the one WCF service.</p>
  
  <p>Setup 2:</p>
  
  <p>Client (Publisher) -> WCF Service (Subscriber)</p>
  
  <p>This one you just increase the number of WCF services to scale (updates would be a nightmare).</p>
  
  <p>I just started looking into the ESB architecture in general so if I'm completely off let me know. I'm essentially just wanting to know what is working for you, and what the "best practice" tends to be.</p>
  
  <p>Thanks!</p>