❔ Event-Sourcing for a Duplicated Topic between Two MicroServices
@Architecture
Hi friends,
I'm working on a project using
Microservices architecture, I have AuthService, ExpenseService and EventSourcererService, the last one is used as a separated service for Event-Sourcing for all other services.
The AuthService is responsible about the User management, it contains a table/entity called User.
In the ExpenseService I need some user's data to be stored in another table inside this service's DB called User, and this data should be the same as in the User of the AuthService.
Oncourse I use the RabbitMQ as the asynchronous communication between my services.
In the EventSourcererService every table/entity in every other services will event-sourced ( their events will stored in the EventSourcererService's DB).
Now the duplicated topic here is the User in the AuthService which the original, and the User in the ExpenseService.
The Issue:
I'm a bit confusing about should I continue with the same flow/method ( every table in every service should have its equivalent events table in the EventSourcererService including the booth users tables in both services) OR create only the event-sources table for only the User of the AuthService OR is there another good approach ?
Please I need an experience share from you and massive thanks in advance <33 Replies
Unknown User•16mo ago
Message Not Public
Sign In & Join Server To View
By ignoring this question, could you please just share with me your experience about this situation??
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.