Akka.net VS Azure Service Fabric
<p>I am learning about Akka.net and have heard about service fabric from Azure. As far as I know, they both are used for building microservices. </p>

<p>Apart from the difference in the scaling model, what else can be the difference between Akka.net and Azure Service fabric.</p>

<p>I see that the conclusion mentioned in the <a href="http://mikhail.io/2016/02/akka-net-style-actors-in-service-fabric/" rel="nofollow noreferrer">following blog</a> gives hint to using Akka.net with persistent storage from Azure.</p>

<p>Can the real-time implementation developer's share their experiences in these technologies.</p>

<p>I find many use cases that can be solved, but one simple one would be a user import process, which typically contains the following steps,</p>

<ol>
<li>Create user,</li>
<li>Add roles to user</li>
<li>Send welcome email to the new user</li>
<li>Manage user based metering for the company to which the user is being added to.</li>
</ol>

<p>I see that all the above steps qualified to contain an actor on its own to perform the activities. Kindly comment on the approach that I have understood.</p>