Service Bus

  1. Add Support for Service Bus Management to the new portal

    On the old portal, I could see and manage all of my Service Bus queues, topics, etc. On the new portal, I am unable to find a way to do that.

    420 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  14 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Provide a Service Bus emulator on a local computer

    Providing a Service Bus emulator on a local computer will reduce development costs.

    149 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    35 comments  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Anonymous responded

    Thanks for this valuable suggestion. We are always working to provide a good developer experience including visual studio tooling to create/update queues etc. We do provide Service Bus on-premise as a developer scenario (this can be run against SQL express as well as on client OS). While not light-weight as an emulator it does provide full symmetric functionality and allows users to use the same messaging features etc. It is a lot of additional cost to provide an emulator when we already provide a full feature on-premise offering that is free of cost. Would like to hear if you have concerns to this approach.

  3. Service Bus Websockets

    Service Bus support for Websockets would be awesome, allowing us to build really scalable real-time web apps.

    Chats & Games
    Stock tickers

    81 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. MSMQ Azure

    Azure Queues are nice, but having a transactional and durable queues with guaranteed only-once delivery would be a big helper. Loosing inherent scalability is OK (just like it works out with the SQL Azure).

    Suggestion in detail is here: http://abdullin.com/journal/2010/5/21/windows-azure-most-wanted-msmq-azure.html

    78 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Anonymous responded

    Thanks for this suggestion, With Azure Service Bus queues you have transaction and several of the other features mentioned. Hope this meets your requirements.

  5. Offer alternative pricing model for ServiceBus connections

    Currently ServiceBus is billed monthly per connection, with prices that can go lower with packs, but nevertheless far too expensive for some low traffic/usage scenario.
    In my scenario the connection is between client applications and the Azure services, must be active all the time the application is working (normally 8 hours a day) and "real" communication between the two, interaction and data transfer, happens unfrequently and move little data.
    In this scenario the current pricing strongly limit the chance to use the ServiceBus, even if it is an enabling feature.
    A pricing model more proportional to time and usage would…

    67 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide ServiceBus tunneling

    ServiceBus requires access to too many addresses and ports when establishing a connection from a published service.

    You should have 1 or 2 at the most ports that ServiceBus uses and everything gets tunneled through that.

    e.g. calls to:
    - accesscontrol
    - watchdog
    - sb-<servicename>...
    - etc.

    Would make configuration MUCH simpler.

    Imagine just opening a couple of ports to a defined IP range, rather than 6 ports to 16 different IP segments - just for one DC.

    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. webhttprelaybinding should support jsonp

    This binding should support JsonP just like the WebHttpBinding supports it.

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Josh Twist responded

    This is already possible, with the appropriate authentication model.

  8. ServiceBus Monitoring

    Create a Azure AppFabric ServiceBus monitoring API to allow near real-time monitoring of ServiceBus Queues, Topics and Subscriptions.

    Some of the metrics that I would like to see:

    1) Total number of messages currently in the queue/topic/subscription
    2) Total number of dead-letter messages currently in the queue/topic/subscription
    3) Total number of messages that have exceded their TTL
    4) Total number of messages over the past N minutes (this could be a fixed number)
    5) Total size of messages currently in the queue/topic/subscriptions.

    This information could be surfaced via a HTTP management API, or through a table storage connection for historical…

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Make service bus HIPPA compliant

    Idea is self-explanatory. The BAA doesn't currently cover Service Bus, but given its purpose, it seems a natural component to want included within the HIPPA compliance.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. integrate signalr with servicebus

    Provide Javascript client library (like signalr client) for ServiceBus

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Implement MSMQ Azure (from Rinat Abdullin)

    Rinat Abdullin: Azure Queues are nice, but having a transactional and durable queues with guaranteed only-once delivery would be a big helper. Loosing inherent scalability is OK (just like it works out with the SQL Azure).

    Suggestion in detail is here: http://abdullin.com/journal/2010/5/21/windows-azure-most-wa... more

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Anonymous responded

    Thanks for this suggestion, with Azure Service Bus Queues you now have several of the features such as transactions and de-duplication in Azure.

  13. Event Bus

    Event Bus with events for storage manipulation (e.g. queue insert) in order to avoid poling.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Extend queue message timeouts

    Sometimes you want to manage messages for long running tasks. The ability to pop a message, (timeout 5min) and process it for 4 hours, updating the message every < 5min to say extend the timeout 'i am still working with it'

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Shared Access Signature Authentication with Service Bus for Windows Server

    So far, I have seen the Shared Access Signature Authentication supported by the Windows Azure service bus but I wish Shared Access Signature Authentication to work with Service Bus on Windows Server

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Anonymous responded

    Shared Access Signature auth is supported in Service Bus 1,1 for Windows Server release (using Azure SDK 2.1)

  16. Possibility to change subscription filter rules

    To have a dynamic service bus, it must be possible to change subscription filter rules. Today, it seems that you have to delete the filter and create a new one.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Anonymous responded

    Thanks for this suggestion. While we do not have a API to modify a rule we do allow you to enclose a rule remove and add in a single transaction boundary. Other related operations like completing or dead-lettering messages can also be done within the same transaction thereby achieving all the functionality needed from a modify operation. Do let us know if there are any particular scenario which are still not possible.

  17. Provide geo-redundancy for service bus namespace

    While I understand the complexities (in flight data will be the issue here?), it would be great to get an option to have a service bus namespace failing over to another data center (like the new SQL Azure geo redundancy), so that in case of a data center outage, we can continue to process messages as part of a disaster recovery procedure.

    We are currently looking to work out of full DR plan as part of our distributed platform offering and Service Bus is one of the complex components, there.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Anonymous responded

    Thanks for this feedback Sam, we recently made available the feature for Send Availability across namespaces (geo-distributed) that allow you to Pair these and if one DC fails then messages are stored in transfer queues until it is available again. We are working towards extending this to Send and Receive Availability but using 2 Active/Active Namespaces (duplicating messages) is the way to achieve that today. These features are different form the disaster recovery procedures we have and allow you to control message flows across namespaces. More details are at: http://msdn.microsoft.com/en-us/library/azure/dn292562.aspx

  18. Support TCP federation through the service bus

    Federated security being so important, it should be possible to enable federation through the service bus, using TCP relay to allow for direct connection. There should be a binding for this that works. Or ,at least a sample that works.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add load balancing for netTcpRelayBinding services

    It would be great to be able to run several instances of my relayed service, connect them all to the AppFabric and have the AppFabric automatically load balance incoming client requests.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Josh Twist responded

    Load-balancing is supported for most Service Bus Relay bindings. You can have up to 25 instances of a listener service connected to a Relay endpoint. The Relay service distributes incoming requests from clients to the connected listeners to load-balance.

    No configuration is required to use this feature. All the instances of the listener connected to a Relay endpoint need to have identical configuration.

  20. Allow co-administrators to manage ACS namespaces for service bus

    Currently, only the primary administrator for a subscription can access the ACS portion of the portal for namespaces. Co-administrators receive an error message when trying to do so. Co-administrators should have the same ability as the primary administrator.

    In my case, the owner of the company I work for is the administrator for the subscription. However, among other things I am in charge of all configuration of Azure. To facilitate this, he made me a co-administrator. Currently I cannot configure ACS when logged in under my own account.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Anonymous responded

    James this should now be enabled, please let us know if it does not meet your expectations.

← Previous 1
  • Don't see your idea?

Service Bus

Categories

Feedback and Knowledge Base