You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to retrieve transactions from the exchanges.
But we want it light weight yet a first step towards using event sourcing (hoping to get some benefits out of a minimal implementation of it)
Ref: https://github.com/commanded/commanded
The text was updated successfully, but these errors were encountered:
We might want to store the original data from the exchange however, not the dumb down data (lowest common denominator between all exchanges).
Not sure how this is doable without doing it in the connector... or exposing the complex data to the web app.
This needs further reflection...
Maybe the xest app should provide some protocol to allow the connectors to "add" event sourcing functionality, when used with xest, but keep xest somehow agnostic to the event datastructure stored.
This requires Review cache / clock design #29 to be done first. The local cache needs a way to choose to use the cache, or retrieve remote, based on data content (the time), and the clock. It is a tricky thing that should be done right as a first step.
We need to retrieve transactions from the exchanges.
But we want it light weight yet a first step towards using event sourcing (hoping to get some benefits out of a minimal implementation of it)
Ref: https://github.com/commanded/commanded
The text was updated successfully, but these errors were encountered: