Open sczyh30 opened 8 years ago
Event driven structure seems nice, but the application requires a large refactor to adapt to the message-based architecture. Perhaps we can add a group of Akka Actor
layer...
And as for event sourcing pattern and CQRS, the Akka Persistence might be a choice, but we need to think carefully about the logic and domain design (as the DDD seems not so easy...)
Planning to do this: make the architecture more event-driven and reactive. May use Akka to decouple components (with reactive streams) rather than invoke services directly.
And event sourcing pattern might also be a good point (e.g. for friend relation events).