I understand the basics of REST + event sourcing I have never worked hard on the RESTABEL API nor did any event In the sourcing project.
Can anyone explain that both can be used together?
In the case of sourcing, the client sends the event, does it mean that there is a collection of events on the server and all the posts of the API will be on that collection, which can add events to it?
How to get the command that the client can send
Can anyone explain that both can be used together? Yes the client (browser) does what he wants to do and (HTT) server can record those tasks as events. In case of sourcing, send client events, this means that the server is there a collection of events and all the positions of the API will be on that collection, to add events for it? No client can be a provider of events, but on the basis of that collection of events, no event should be formed to prevent tight coupling between the server and the client. Event sourcing should be explained and hidden from the actor. How can the client get the order that he can send to the server? This is not necessary if you do not need to send an event to the same collection as you have suggested in your previous question. You want to publish just a REST API in any way and hide the event of sourcing from the client / actor. See.
No comments:
Post a Comment