Skip to main content

Azure Traffic Manager - How to use on-premises endpoints

Some weeks ago I wrote a short blog post about Traffic Manager. It is a great service that can be used to redirect traffic to the closest datacenter, redirect traffic in a balanced way (Round Robin) or to be able to redirect traffic to another location when an endpoint goes down.
For more information related to it please visit the following blog post: http://vunvulearadu.blogspot.com/2013/07/traffic-manager-overview.html
But let’s see what else we can do with Traffic Manager. Of course we can register very easily endpoints from Azure, this is normally. But you should know that it is possible to register public endpoint that are hosted on on-premises system or why not on other clouds providers.
This features is the kind of feature that can make your life easier. Why? Why not have endpoints on-premises and use Traffic Manager only for redirecting purposes, in case of failover and so on – almost like a load balancer, but without the ability to read the load of each endpoint (this cannot be done using Traffic Manager, but is full supported out of the box by the Load balancer from Azure – and is free!).
If you create a new Traffic Manager instance, you will see that you can register endpoints only from the same subscription and ONLY the one that are hosted on Azure – from the Azure portal. If you need to register an endpoint that is hosted on on-premises servers, than you need to do this by hand using PowerShell or the REST API.
REST API: http://msdn.microsoft.com/en-us/library/azure/hh758257.aspx
PowerShell: http://msdn.microsoft.com/library/dn690257.aspx
Why we cannot do this from portal? I don’t know, but it would be nice.
In both cases it is important to set the ‘Type’ of the endpoint to ‘Any’. Otherwise, you will add the endpoint as other endpoint.
PowerShell Sample:
Add-AzureTrafficManagerEndpoint 
  -TrafficManagerProfile $TrafficManagerProfile 
  -DomainName "foo.onpremises.com" 
  -Status "Enabled" 
  -Type "Any" | Set-AzureTrafficManagerProfile

Enjoy!

Comments

Post a Comment

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