Skip to main content

(Part 1) Azure Service Fabric - Parent Child communication and cancellation

Part 1 - http://vunvulearadu.blogspot.ro/2016/03/azure-service-fabric-parent-child.html
Part 2 - http://vunvulearadu.blogspot.ro/2016/03/part-2-azure-service-fabric-parent.html

A few weeks ago I so an interesting question on MSDN forum that I think that is pretty common. In this post I will try to give a possible solution to this problem.
Context:
There are multiple instances of the same Restful Stateful Services that are running in parallel. A new instance is created by a 'parent service that also might specifies the action that needs to be executed.
Problem:
The parent service needs to be able to cancel the instance of our Restful Stateless Service based on external factors or based on the current state of the child.


What we need
Basically we need to:

  • Store and map all the service instances that are created by a service
  • Store in a specific location a state related to them
  • Share their state with the parent service
  • Give the ability to the parent to cancel a child service
Sharing the state
To be able to share the state between different instances of the same service we can use Reliable Collections. In our case Reliable Dictionary might be a good solution for our problem. We can store as a key value pair the state of each service instance. 
Each instance has the ability to update his state directly. Any concurrency problem like temporary inconsistency are resolved out of the box by Reliable Dictionary.

Cancellation
When we create an instance of a Restful Stateful Service we can use RunAsync method. This method allow us to specify a cancellation token. This token can be used by the child service to see if a cancellation was requests.
protected override async Task RunAsync(
      CancellationToken cancellationToken)
{
    ...
}

Unique identification of each child service
In our Reliable Dictionary we need to identify unique each service. We could generate a unique ID for each service instance. It might work, but we would need to send this ID to each service instance in the moment when we would call RunAsync method.
Another possible solution is to use the CancellationToken that we already have as a key. The instance of cancellation token is known by parent and child  we can use it easily as the key.


Using this approach we can have a mechanism that allow us to have a simple and cheap communication between our services. The main flow would look like this:

  1. [Parent] Create a CancellationToken
  2. [Parent] Add the CancellationToken to our Mapping State dictionary 
  3. [Parent] Start a new instance of your stateless service and give us parameter the CancellationToken
  4. [Service Instance] Do his logic
  5. [Service Instance] Add specific information to the Mapping State dictionary to the item with the same CancellationToken
  6. [Parent] Detect that a condition is TRUE
  7. [Parent] Get the CancellationToken of the service instance that needs to be canceled
  8. [Parent] Send the CancellationToken to the service instance
  9. [Service Instance] Detect the cancellation request and stop


This solution can be very useful when we need to migrate a heavy services from a monolithic architecture to a solution hosted on a micro-service system.
The only problem with this solution is related to the type of service. We cannot use multiple types of Reliable Services for this because a Reliable Collection can be shared and accessed only by the same service type.

Tomorrow we will see another solution for this problem without having to use Reliable Collection and the same Reliable Service.

Part 1 - http://vunvulearadu.blogspot.ro/2016/03/azure-service-fabric-parent-child.html
Part 2 - http://vunvulearadu.blogspot.ro/2016/03/part-2-azure-service-fabric-parent.html

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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.51 EF 6.0.2 VS2013 It see...