Skip to main content

Scheduled Backend Tasks - Windows Azure Mobile Services

Using Windows Azure Mobile Services we can create in a short period of time a simple backend for our application. In the last period of time a great feature appeared – Scheduled Backend Tasks
This feature permit users to create jobs that can run at a specific time interval. Imagine that you have an application that track the GPS location of users for the last 6 hours. All the information those are older than 6 hours can be removed. This problem could be solved by a manual trigger, but we are the XXI century, everything needs to be automatized. In this case you would have a job on a server that would make this cleanup. But wait; way would you need something like this when Mobile Services give you the possibility to create your backed very easily.
The scheduled job support gives us the possibility to create a job that run at specific time intervals or demand. Each job that is created can be enabling or disable anytime. Also, jobs can be run manually, using the “RUN ONCE” functionality. 
The language that can be used to define each job is JavaScript. It is the same language used to define custom scripts over tables from Mobile Services. From this job we can execute any kind of code over tables from Mobile Services or we can call remote services. You can imagine any kind of scenarios. The script need to added from the Windows Azure Portal, in this moment there is no support to define it in Visual Studio and make a deploy.
I tried to find what are the current limitation (January 2013) of Scheduled Backed Tasks. What I found until now is:
  • The smallest time interval is 15 minutes
  • Modules supported in this moment are: “azure”, “sendgrid”, “request” (but this list will expand)
  • There is no maxim time limit and you don’t pay for computation time. BUT (yes, there is a but), if you run scripts that drain the CPU that the task will be terminated
Don’t forget that scheduled backend task can be used with success when we want to use push notifications at a time interval. Another case when you can use this feature is to test custom scripts that are defined over tables from Mobile Services.

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…