Actor model communications must implement reliable messaging
At the moment when using ActorModel you may get duplicate messages sent from the client when client gets communication errors or server failure. That in fact means that in the every actor you have to have a logic that will need to understand if message was processed already ot not. This is a standard problem and must be handled by Fabric insfastructure by implementing "reliable messaging". So the framework should detect if it is a duplicated message that already been delivered & processed or not.
@Justin : you can have a flag to enable/disable duplicate filtering, so when perf. is an issue you disable it. But having the option to filter in the fwk can save dev time, I agree with the OP
Justin Stuparitz commented
Wouldn't this hurt performance even more? Service fabric already has "at least once" delivery which comes at a price. Certainly Akka doesn't offer such guarantees. It is left to the implementer and the business logic.