Thank you all for the valuable input!
The design in the (quite simple) scala-code is what my team is currently
trying out, and we are experimenting with various ways of keeping the
amount of code down, yet the most important task for us is to keep the code
understandable.
So far we have had
It is still not a trivial task to do this and keep your business logic
clean and separated from the persistence part. From my experiences the
following makes things more complex:
- It is not necessarily a 1:1 relationship between commands received and
state changes. One received command may
Hi Anders,
You asked for a more advanced sample.
Here is one: http://typesafe.com/activator/template/akka-cluster-sharding-scala
Unfortunately it has not been ported to java yet, but you might be able to
understand the design.
The idea is that you always change the state by applying the stored
