When Service Broker was introduced in 2005 I tried some simple "Hello World" examples which were supplied in order to demonstrate its ability to send messages from one session to another. I didn't need such a tool and wondered who needs it..
It took me some years to discover its ability to execute stored procedures asynchronously, and I have already implemented it in some systems.
I have asked some of my colleagues about Service Broker, many of them use his asynchronous ability to execute procedures, none is using it to send messages.
My question: I suspect the original intention was to supply a messaging system and the asynchronous execution was only a sub product, but somehow - the sub product became a main product. Is it true? Otherwise - do you know many messaging systems rely on Service
Broker?
I ask this question because I don't have any explanation why is it so complex and why I have to create so many objects (message type, queues, services, contracts etc.) which are essential for messaging and
not for asynchronous execution.
Thanks!
El castellano no es mi lengua materna. Discúlpenme por los errores gramaticales, y, si pueden, corríjanme en los comentarios, o por correo electrónico. ¡Muchas gracias! Blog: http://about.me/GeriReshef