Hi Ross,

The short answer is that the second option is currently all Service
Broker can do. It doesn't natively talk to anything but another SQL
Server database/instance/server.

As Paul wrote, check out Roger Wolter's book from Rational Press.

Cheers,

Chris

On Jul 10, 2008, at 10:04 PM, rjempo@... wrote:

> Hello,
>
> I was wondering if anyone can point me at some material, or offer
> any suggestions regarding the Service Broker.
>
> I am evaluating whether the Service Broker can be used as a fire and
> forget style 'message bus'.
>
> By which I mean whether it has the capability to call external
> services (say a WCF service) / programs, and what the best practice
> is for architecting such an infrastructure.
>
> eg, Does it offer the follow features :
>
>
> some app or 3rd party -> WCF -> message on a queue -> message
> filtered / processed based on a 'policy' -> message passed onto a
> different 3rd party service (WCF) -> acknowledgement -> retry ....
>
>
> OR
>
> is it more useful as a simple queue that can pass messages between
> SQLServer instances
>
> I realise you could hand-roll the processing / filtering and
> forwarding of messages to a 3rd party service, and use the Service
> Broker as the underlying queue, but wondered if it could offer more?
>
> Cheers.
>
> Ross
>
>
>
> to unsubscribe to this list, please send a message back to the list
> with 'unsubscribe' as the subject. Powered by mailenable.com - List
> managed by http://www.readify.net
>
>



to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net