Aaronontheweb on fix-di-typo
Aaronontheweb on dev
Fixed a typo with `dependency-i… (compare)
Aaronontheweb on fix-di-typo
Fixed a typo with `dependency-i… (compare)
Aaronontheweb on dev
Akka.DependencyInjection.Servic… (compare)
So I'm working on an application that will have Aggregate Roots like in DDD. I currently see the need to have an actor that given a message, figures out the target entity type and then "activate" the persistent actor for that given entity (by id).
In doing research I came across this statement in the Akka.Cluster.Sharding module:
Cluster sharding is useful in cases when you want to contact with cluster actors using their logical id's, but don't want to care about their physical location inside the cluster or manage their creation. Moreover it's able to rebalance them, as nodes join/leave the cluster. It's often used to represent i.e. Aggregate Roots in Domain Driven Design terminology.
Is my use a canonical example for using cluster sharding? What if I have usages of this pattern that aren't clustered but only have 1 node?