Akka in .Net Core – Part 1 (Creating an Akka Actor)
Designing Akka.NET Applications from Scratch Part 1: Go with the Flow
Zoran Maksimovic - Akka.NET Succinctly
Akka Message Delivery - At-Most-Once, At-Least-Once, and Exactly-Once - Part 1 At-Most-Once
How to Guarantee Delivery of Messages in Akka.NET:
All in-memory message passing within one application, for instance, is going to be guaranteed unless you hit an OutOfMemoryException or any of the other standard CLR failures - those failure cases are no different than what would happen if you were invoking methods instead of passing messages.
You need guaranteed delivery (only) when you’re passing messages over the network.
Why You Should Try to Avoid Exactly Once Message Delivery: use idempotent data structures (to allow for duplicate messages) in the at-least-once systems.
Use async/await only inside of ReceiveAsync<T>.