Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

How can we improve Azure API Management?

← API Management

Socket (full-duplex) support in addition to HTTP

Having the ability to regulate and monitor HTTP services with API Management is great. Wouldn't it also make sense to offer the same for web sockets (or SignalR hubs, etc.) so we can let devs hookup into stream of events (live-data) instead of polling with REST calls?

1,218 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Valery Jacobs shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

32 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    I don't understand how this request has not yet been implemented, when many other alternative solutions allow websockets ! And the original request is 7 years old now...

  • Lou Krieg commented  ·   ·  Flag as inappropriate

    We are designing a new service around web sockets in addition to REST APIs... would really like to be able to support this via APIM for ease of management!

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please can you consider adding this feature. It would allow us to standardise everything behind APIM and make our solution that bit easier.

  • Brian commented  ·   ·  Flag as inappropriate

    websockets is a great feature, we need it. please add support for websockets. more and more CDN support websockets nowadays, why Azure can't provide support for this feature?

  • Ries commented  ·   ·  Flag as inappropriate

    Any updates Microsoft? Or do we need to switch to AWS, because they allow websockets just fine.

  • Jeremy commented  ·   ·  Flag as inappropriate

    I think the use case is simple. We have an API that uses SignalR and it needs to be behind a gateway to fit the current infra architecture. Our enterprise uses APIM as a gateway and would rather not have to stand up application gateway separately and incur that added cost.

  • Jeremy commented  ·   ·  Flag as inappropriate

    @michaelpapasvastos

    > Why wouldn't someone just use Azure SignalR service for this?

    Because it's not a gateway.

  • Anonymous commented  ·   ·  Flag as inappropriate

    As well as supporting websockets, it would would be better for the service to break the connection between the client and hosting service. At the API Gateway level we should be able to inject rules for checking format, security rules and possibly re connection logic as needed.

    Client <--> API Gateway <--> Host

  • Rizvan Bhimani commented  ·   ·  Flag as inappropriate

    We want to use socket.io functionality with api-m but it is still not available. Latest technology should support by azure.

← Previous 1

API Management: Defining APIs

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice