Skip to main content

Azure Service Bus Topics - How communication works over HTTP (80,443)

In this topic we will talk about different protocols and ports that can be used to communicate between our machines and Azure Service Bus Topics.
The communication between Azure Service Bus Topic and our machines we can use:
  • AMQP (new and hot)
  • TCP/IP
  • HTTP
For TCP/IP connection is pretty clear what ports are used (9351 and 9552). It seems that 9351 is used for inbound traffic and 9552 is used for outbound traffic (this ports may change)

The interesting discussion is when we are taking about HTTP. The communication over HTTP protocol is done over two ports - 443 and 80.
Each port is used for specific use case:
  • 80:   is used for outbound traffic
  • 443: is used for inbound traffic
This means that when we are listening to a subscription we will use port 80 to check if a message is available. The same port will be used to receive the message from subscription. 
The port 443 is used when we need to send messages to topic. Each time when we send a message to a topic, the message is send over 443 without exception. 

For both ports (80 and 443), the communication is done done using a TLS/SSL. Even if port 80 is used, the communication is secure - inside a tunnel. No data in clear are send between our application and Azure Service Bus.
It is important to know that Azure Service Bus doesn't supports unsecure connection. All the communication will be done over a secure tunnel.


If the connectivity mode is not change (AutoDetect), the Azure Service Bus library will try to use TCP/IP connection. If the connection cannot be established using the 9XXX ports, it will fall back automatically to HTTP ports.
We have the possibility to specify directly what kind of connectivity mode we want to use (AutoDetect/TCP/HTTP). This is useful when we already know the connectivity type. 
The below sample shows how we can configure it.
HTTP: ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Http;
TCP:  ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Tcp;
Auto: ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.AutoDetect;

In conclusion we should keep in mind that all the communication between Azure Service Bus endpoint and our system is done over a secure channel. For HTTP connection, a tunnel is establish over 80 and 443 ports.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP