12 Comments

  • Janusz Maksymowicz

    Hi there. This is nice video but very low informative. After 13:38 min I still don't know what Service Broker is and what is the purpose of using it. You are talking like a robot or bored teacher on the same 1001 presentation. Please explain what Service Broker is, what is his purpose in general in simple words, put some simple non-technical diagram of it – like "if there is a 100 application, service broker is able to parallel the request from application or balanced the resources between application requests". In way that almost every technical person will understand. Not only some "few geek developers from your room in school". Come on, it's a video for people. BR,

  • Janusz Maksymowicz

    Oh, and put some energy and positive attitude in your videos. Talking like a robot without any intonation is very hard to listening and understand above 1-2 minutes.

  • autecuso

    It sounds like Service Broker could be customized to create a custom company-wide trouble-ticket/change control system when used in coordination with an sql server database.   Kewl.

  • Asif Ashraf

    I am happy to know service broker. But SCALEOUT is a totally different concept. This means attaching more outsided resources to handle the load. You have not spoken on that point. How service broker can help on-demand in that regard?

  • VProjects

    Thanks for the informative video, I like the way you deliver the information – straight to the point.
    Back in 2005 I was excited by Service Broker (SB) intro, but actual implementation found cumbersome and we stopped supporting SB.

    Question: in these days (2018) how would you build asynchronous SQL queries processing?
    Would you still consider SB for messaging?

  • Brandon Miller

    Thank you for posting this video. I'm wanting to do distributed computing. Right now, our system is dumping into a SB Queue and it activates several threads to process the queue inside of SQL Server. However, the CLR that it is calling downloads HTML from a website and sends it to an SMTP server. For whatever reason, this is much slower than taking the processing outside of SQL Server. I would like to write a distributed .NET Core app that works on the existing queue and make sure that it does not duplicate the work. Our customers do not want to receive multiple emails and they definitely want their email. Before, I relied a lot on SB to handle all of that and now I'm not sure what would happen if one external app received an item and started processing, but didn't complete.
    I've been searching for applications that have used SB and it is very hard to find them. They almost always use RabbitMQ.
    What are your thoughts?

  • Hari Hariprasad

    Jon, I love your videos for their content. They are very informative. I also like your delivery style. Thanks for sharing your expertise! Keep up the good work.

Leave a Reply

Your email address will not be published. Required fields are marked *