Why do I need two SQL Server Service Broker queues for a simple task?

Question

All examples I find on the web for using SQL Server Service Broker queues seem to have two queues. I don\'t understand why and every example seems to assume that this is so

Answer 1

Service Broker has basically nothing to do with queues. Service Broker is for writing distributed applications, not for queuing. Queues are simply message stores for service, and one service is on one machine while the other service is on a second machine. Examples may show both services in the same database just for simplicity sake, but the example is still about communicating in a distributed environment.

Examples that show case where a single queue apparently is enough are using Service Broker incorrectly. Those examples should better show how to use tables as queues.