Service bus should not charge for registering an endpoint.
Apparently, the sb charges when you register an endpoint and not when a connection is made.
DavidSnipp
shared this idea
2 comments
-
Vossekop
commented
This is something we are looking at as well. For v1 i will probably try a polling mechanism using either Azure storage (queues) or a service endpoint. But something that works out of the box would be a heck of a lot better if you ask me.
-
Chris Mankowski
commented
I agree, we need an option to "register" an idle Service Bus connection that we aren't charged for.
Here is the use case summary of that MSDN link: Consider the situation where the SB is used as a support lifeline for a distributed application installed on 10,000 PC's. As it stands today I only have the option to create an idle connection with the service bus. I could invent a workaround by creating a HTTP polling mechanism to ask the server if the Service Bus should be activated... and then write the code to activate the SB connection. Considering that this is a service of considerable scale, I'd like MSFT to apply thier knowledge of how to achieve this with efficency in mind.
I would be excited to see something like this surface as an option within the AppFabric SDK.... although I'd be equally interested to see an implementation (whitepaper, blog, etc) for the current version.
