What Gets Lost, What Doesn't, and Why Restarts Help Build Better .NET Applications
One of the most powerful features of Akka.NET actors is their built-in fault tolerance. Actors are an extremely effective tool at isolating failures and preventing them from having side effects on other parts of your application.
However, one of the most frequently asked questions we hear when training .NET developers on the fundamentals of Akka.NET is: “what happens to my data when an actor restarts? Do I lose messages? State?”
We address those questions in this tutorial.
This video covers:
- How Akka.NET actors are supervised and restarted by their parents when they crash;
- The internals of how individual actors are constructed and the role these parts play during restarts;
- How restarts are made transparent to other actors via
- Why these properties can ultimately help build more resilient and effective .NET applications.
If you like this video please share it and subscribe to Petabridge’s YouTube channel!If you liked this post, you can share it with your followers or follow us on Twitter!
Upcoming Petabridge Live Akka.NET Webinar Trainings
Get up to speed on the leading edge of large-scale .NET development with the Petabridge team. Each training is done remotely via webinar, lasts four hours, and will save you weeks of trial and error.
|Akka.NET Application Architecture and Design Patterns|
|Building Networked .NET Applications with Akka.Remote|
|.NET Distributed Systems Architecture and Design with Akka.Cluster|