Skip to main content

Azure CDN – Solutions for things that are not available (yet)

Last week I had some interesting discussions around payload delivery and CDNs. I realize how easily people can misunderstand some features or functionality, thinking that it is normal or making the wrong assumption.
In this context, I will write 3 posts about Azure CDNs, focusing on what is available, what we can do and what we cannot do.


Let’s see what we can when we need to do when we need the Azure CDN features that are missing in this moment in time. In the last post we talked about this features, we will not focus on explaining them – for this please see the previous post.

SAS Support for Blob Storage
If you need on top of Azure Store, a CDN system that has support for SAS, then you need to be inventive. The simplest solution is to replicate the content in multiple Azure Storage Accounts or even in the same Storage Account (if the problem is download speed) and create a web endpoint (that can be hosted as a web app), that will provide the locations from where the content can be downloaded.
This web endpoint, can have a Round Robin mechanism (the simplest thing) to serve different locations.

Using this approach, you will also need a mechanism that replicates the content in multiple locations. AzCopy might be a good out of the box solution.

HTTPS for Custom DNS Domains
The same store with Azure CDN is with Azure Storage. In this moment we don’t have yet support for HTTPS and Custom DNS Domains. In this case if you really need HTTPS, then the only solution is to serve the content from an Azure Web App. There not to many options for now.

HTTPS Client Certificates
The story is similar with the previous one. We don’t have to many options. The best way for now is to use an Azure Web App and serve your binary content from there.

HTTP/2
None. As above an Azure Web App.

Fallback to custom URI
For this situations, we have a simple solution. We can go with the approach presented in the SAS Support example. The additional thing that we need to do is to have multiple Azure Web Apps that can server the content location and add an Azure Traffic Manager in front of them.


Access logs of CDNs are raw data
If you really need this logs, then you need to use Azure Blob Storage. The above approach and activate logs in each Azure Storage Account.

As we can see, there are so many features support by Azure CDN. Of course we will not be able to find a perfect solution that supports all the things that we need. The same is happening with Azure CDN. But what is important to remember that a part of the features that we are missing are already marked as In Progress in the feedback portal of Azure. This means that soon, we will have support for them also.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…