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 per
DREAMER, CRAFTER, TECHNOLOGY ENTHUSIAST, SPEAKER, TRAINER, AZURE MVP, SOLVING HARD BUSINESS PROBLEMS WITH CUTTING-EDGE TECHNOLOGY