how i know the concepts about event soucring that important events of app are stored on event store databases. but there are many prallel questions.
1) how main DB works in this application? for example when wi store a data like (player transaction added 100 golds) how main database that stores current state of player/user should be used. can i do a CRUD to update the main database in other microservices or its different?
2) how SAGA benefits from event sourcing. does it benefit at all? for example when one of the microservices failed and we want to compensate the whole scenario, do we need to use event sourcing for that or an inner state memory is enough?
3) what is the best practice saving user events in event stores? as you may know event stores can get very big soon. assume that based on some condition we want to remake a user current state from its events? what is the right approach?
Top comments (4)
i think projection is used to update the main database to apply the event on main database. right? i think orchestration is a must to make sure that main database is synced with events store.
another question is: is there any standard implementaion for event sourcing or any type of saving sequence of events is called event sourcing. martin fowler example is in c# as i needed but i could not find the project implementation of it on github or somewhere else.