2 ms·
Somehow I feel this is the data modelling tool but looks like it can also modify source data? What is the use case of modifying the source data? I'd prefer to k
by markus_zhang 2y ago
Somehow I feel this is the data modelling tool but looks like it can also modify source data? What is the use case of modifying the source data? I'd prefer to keep everything as is and do transformation afterwards to clean up.
I'd also recommend brushing up the doc. There is not a lot of things there (but we already reach v2?) and the Flowcathon seems to be the first thing a developer needs but it needs an account.
- odinellefsen 2y agoHey thank you for taking the time to look at our docs :heart. The event history is append-only, so we keep the raw data immutable. When we talk about replaying it's about reprocessing the events through improved flow logic or to build new read models, but not changing the original events themselves. You mentioned Flowcathons, these are actually just little workshops that we had for some local tech companies to try out the platform :)
- odinellefsen 2y agoIt’s basically immutable event sourcing with built-in replay and read model flexibility, without needing to build the whole infra stack yourself. You just send an event via a webhook or filehook to the "Data Core", and then via our cli command or the ui you can stream the data from the "Data Core", in the order it came in, anywhere you want. But in the case of an actual application you would need events to be acted on instantly, like creating a user you would want it to be stored in the db immediately. This is where our "Transformers" come in.