Skip to main content

Azure Service Fabric - Actors and Reminders execution order

The main topic of this post is the order execution of requests that are coming to a Reliable Actor of Azure Service Fabric.

Actor and Single-Thread
Of the most important characteristic of an Actor is that is single-thread. This means that if you have 3 different requests that are coming to the Actor, the actor will execute them one at a time.
As we can see in the above example, while the actor execute the first request, it will not start executing the second request. All the requests will be added to an 'execution queue'. In this way, there will be only one thread executing in the same time on an actor.
This is why, all the functionality that is exposed by an actor is asynchronous and should all the time have a cancellation token. We might have cases when we want to cancel a request because of a timeout or other causes.

Reminders
On top of this we have Timers and Reminders that are used in combination with an Actor when we want to execute a specific action after a period of time. For example we have an actor that checks every 10 minutes if new content is available for him or we can have another actor that checks every 12 hours if the commands that are stored by him are expired or not.

Execution order
Now, in combination with the execution flows, comes the big question. If we already have Request 2 and Request 3 in the 'execution queue', when our reminder will be executed?

We might have a clean-up or check action that needs to execute every 10 minutes. If Request 2 and 3 takes to much, we might end up executing the Reminder action to late.

It is important to know that the priority of an action triggered by a Reminder is higher than a normal Request that arrives to an actor. Because of this, the Reminder action is executed immediately after the current request.

This means that even if we have Request 2 and Request 3 in the 'execution queue', the Reminder action will be executed once the Request 1 ends. Even if Request 2 and 3 arrived before the Reminder action, the Reminder will have a higher priority.

Conclusion
It is important to remember that:

  • Each request (action) is executed one at a time
  • If actor is executing another action, the second action will be putted in a queue until the first action is executed
  • The action that is triggered by a reminder will be putted in the 'execution queue' with a higher priority

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…