azure-sdk-for-net
azure-sdk-for-net copied to clipboard
Azure
Documentation: pros and cons of Amqp vs AmqpWebSockets
So that help page describes what to use:
- Amqp | 0 | Uses AMQP over TCP. This is the default value. It runs on port 5671. (ok that's kinda good to know)
- AmqpWebSockets | 1| uses it over webSockets. (also kinda obvious from the name)
What's missing is a bit of an explanation of the pros and cons of using one or the other. When should we use Amqp, and when should we use AmqpWebSockets. What are the implications. If it requires more than a paragraph to get the gist of the difference, please link to a longer blog entry or similar.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: fc77eef1-62e7-007a-20bc-94c9a22b4f93
- Version Independent ID: 26fa7c4a-b015-ac4b-340f-cc531e53d638
- Content: TransportType Enum (Microsoft.Azure.ServiceBus) - Azure for .NET Developers
- Content Source: xml/Microsoft.Azure.ServiceBus/TransportType.xml
- Service: service-bus-messaging
- GitHub Login: @rloutlaw
- Microsoft Alias: routlaw
Thank you for your feedback. This has been routed to the support team for assistance.
@tomeberhard There are mentions of the difference in this protocol guide doc.
The main difference is that WebSockets are used for underlying connection which is over port 443. This could be useful in cases where networks where the clients are running block all other ports for security reasons.
Apart from the underlying connection, the AMQP aspects are still the same.
Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!