Shulou(Shulou.com)06/01 Report--

What are the different ways to implement the Actor model in .NET? I believe many inexperienced people are at a loss about it. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Vaughn Vernon, author of implementing Domain driven Design (Implementing Domain-Driven Design), released Dotsero, a .NET-based Actor model toolkit written in C # whose implementation refers to Akka API. The Akka toolkit is an implementation of the Actor model, and so far there are corresponding Java and Scala versions of API.

Earlier this year, Microsoft's Research division also released a framework based on the Actor model, a preview of the Orleans framework. This framework uses a cloud programming model and is written to minimize the challenges faced in creating interactive services that often require high scalability and reliability.

The Orleans team believes that while Actor platforms such as Erlang and Akka have taken a step forward in simplifying distributed system programming, they remain highly complex because they provide relatively low levels of abstraction and system services. Developers must become experts in distributed systems before they can use these tools to create the right solutions. To avoid these complexities and attract mainstream developers, the Orleans team raised the level of abstraction of Actor. Although it is still based on the Actor model, it differs from any existing Actor model-based platform in that it treats Actor as an abstract rather than a physical entity.

Recently, Sergey Bykov from Microsoft's Research division, the leader of the Vaughn and Orleans project, had a discussion on twitter. According to Vaughn, Orleans is not essentially an implementation based on the Actor model, in part because it lacks the Become and Unbecome methods to support finite state machines (FSM), which Vaughn believes are a necessary part of the original definition of Actor. He also believes that because Actor always exists in Orleans, it is difficult to realize this when a client initiates a request to an Actor that should not exist, which can easily lead to problems.

In response, Sergey said that Become is just one way to read the definition and is not a necessary part of the Actor model. From his experience, because the Actor in Orleans always exists, the generation of race conditions is reduced and the recovery operation is simplified. From this point of view, the possibility of problems is much less than that of Vaughn. If an Actor should not exist, it can be handled by returning an error state by the application logic, which he admits is not ideal, but it is better than encountering a race condition when creating an Actor.

Recently, a Microsoft MVP,Richard Astbury in Azure created a simple Internet of things gateway application to demonstrate his view of Orleans that Orleans can help developers create large-scale, low-latency, and adaptable .NET applications in the cloud. Richard says that while this is a simple example, it already includes the various basic building blocks needed to create more complex scenes.

After reading the above, have you mastered the different ways to implement the Actor model in .NET? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.