The Reactive Monolith – How to Move from CRUD to Event Sourcing

Re:The Reactive Monolith – How to Move from CRUD to Event So... by y4mi on Thursday September 30, 2021 @03:31AM (#28703996)

it sounds pretty straightforward to implement with basic crud too, though. you'd just need an inserted timestamp field so that you can rerun the analysis with

    where inserted >= the_date
    order by inserted

[ Parent | on HN ]

Re:The Reactive Monolith – How to Move from CRUD to Event So... by nivertech on Thursday September 30, 2021 @04:13AM (#28704176)

I think GP mixing up Stream Processing with Event Sourcing [1]. Event Sourcing is usually used in complex business domains, Stream Processing in simple domains, but with large amounts of data (i.e. IIoT).

if you use a timeseries databases like kdb+/q, TimescaleDB, InfluxDB, QuestDB, etc., you don't even need to order by the insertion timestamp.

Unlike RDBMS/SQL where rows/tuples are unordered, in timeseries databases they're usually ordered by the insertion time, more similar to dataframes than to SQL tables.

[1] Martin Kleppmann — Event Sourcing and Stream Processing at Scale

https://www.youtube.com/watch?v=avi-TZI9t2I

[ Parent | on HN ]