4 ms·
I'm taking a cautious approach (as with any new libraries), but so far it's been in a couple of small projects in production and working well. It is certainly
by hhandoko 12y ago
I'm taking a cautious approach (as with any new libraries), but so far it's been in a couple of small projects in production and working well.
It is certainly far easier to write new implementations with Akka.NET in mind. But there are a couple of strategies that I found useful in retrofit scenarios:
1) Use adapter / proxy patterns (with DI / IoC). A bit tedious, but easy to back away from.
2) Use async more. It does force you to adopt a certain mental model, which helps make the transition to Akka a bit easier (rather than returning Task<T>.Result everywhere from Akka actors).