Timeline for What is a good technique to process an event stream to ensure sequential or transactional consistency
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2019 at 3:57 | vote | accept | scipilot | ||
| Mar 25, 2019 at 22:52 | comment | added | Kain0_0 | @Neil Yes, you would need to handle errors. The problem with not trying to rationalise the data and reprocess it instead comes down to what is meant by "processing a request". If its an idempotent and/or reversible action then your fine. But when its an irreversible action or it is reasonably expensive to undo a previous decision then you need to be careful, or atleast need to minimise the opportunities for mistakes. | |
| Mar 25, 2019 at 22:47 | comment | added | Kain0_0 | @scipilot good point, I deed mean Service Level Agreement. I've updated my answer to detail that. | |
| Mar 25, 2019 at 22:45 | history | edited | Kain0_0 | CC BY-SA 4.0 | added 29 characters in body |
| Mar 25, 2019 at 8:40 | comment | added | scipilot | Markov Chain looks interesting (although slightly overwhelming). I am trying to avoid knowing anything about the upstream provider and specifically "fixing" it, as it's likely to change which would then break me. But I do in fact know more about why some of the data is actually reversed and mixed with other types - that's mainly due to processing delays in different event types, rather than different devices, and due to to parallel event message queues. I like the probabilistic approach as I think there are some unknowables in there. | |
| Mar 25, 2019 at 8:31 | comment | added | scipilot | By SLA you mean Service Level Agreement? Or is this another term? | |
| Mar 25, 2019 at 8:18 | comment | added | Neil | This could work, but it's lacking error handling. Considering that the worst case scenario is "processing the same request twice", an argument could be said for simply leaving it as is. | |
| Mar 25, 2019 at 6:59 | history | answered | Kain0_0 | CC BY-SA 4.0 |