These are chat archives for akkadotnet/akka.net
me again. So I'm trying to test that on receiving a particular message the actor throws out of the handler (expecting in real life that the parent will apply it's directive). I've initially got the following, which I thought would work, but isn't. Can someone suggest a better solution or shed some light on why this isn't working please?
public void test_actor_dies_on_some_message()
var died = false;
var actor = this.ActorOfAsTestActorRef<MyActor>(Props.Create(() => new MyActor()).WithDispatcher(CallingThreadDispatcher.Id)
.WithSupervisorStrategy(new OneForOneStrategy(e =>
died = true;
actor.Tell(new SomeMessage(new Exception("noooooooooo")));
WithSupervisorStrategyis the supervisor strategy that is applied to that actors children, not to the actor itself
@ronnyek to be honest I think, this is more matter of what kind of people team is made of and specifics of the problem, you're trying to solve.
Of course while both Akka.NET and Orleans cover similar fields, some of them are more towards one technology than other i.e. data analytics and high-performance computing for akka while orleans more for scaling out business domain logic with low consistency constraints - at least at the present moment, until cluster-sharding is not ready. And I'm a "little bit" biased, but from my perspective akka is superset of orleans, because it has lower baseline, which allows making more things possible, and extensible so higher levels of abstraction can be just plugged on top of library. Eventually all features of orleans (even project orleans itself) could be implemented in akka - but not vice versa.
However how does this maps to first sentence? In general akka.net gives you more control, it's more toolkit that allows you to build your own "framework" accordingly to your needs - when working with it, you're actually building your own abstraction layer on top of it. But this also enforces more responsibility from the team and ability to program in paradigm that is not inherently OO. And this requires an understanding of problems and solutions in domain of distributed computing and actor paradigm itself. Orleans is proud of it's low barrier of entry - but I would call this AngularJS paradox ;) Also each framework has some tradeoffs and limitations - you need to understand how well does it fit in your case, because at some point you may hit the barrier, that framework you use, was not prepared for.
can anyone explain this json
Propsand other primitives that contains arrays of
object, we need to know the type
TestActorOf, for instance