Akka is much better fit for event sourcing architectures, and eventual
rather than global consistency (implied by ACID).
Regarding coordination of different services, the typical approach of Akka
applications is the saga pattern and compensating transactions.
"Reactive design patterns" by dr R.
Hi,
The FSM JavaDoc mentions a convenience matcher called Ev for matching
events without the data, but I can't find the actual matcher (or any
reference to it in the main docs). Does it actually exist, or is it a "bug"
in the JavaDoc?
Thanks,
Tal
--
>> Read the docs:
