News for hackers. Stuff that matters.
Re:PranaDB – A distributed streaming database, designed to b... by guywhocodes on Friday April 29, 2022 @11:10PM (#31213029)
This is quite interesting, at $work we use kafka and postgresql / other transactional databases. And we are probably over a man-millennia of work invested in making data consistent between the two. Given a lot of that is based on mindless "REST over Kafka"
Re:PranaDB – A distributed streaming database, designed to b... by jitl on Friday April 29, 2022 @11:36PM (#31213143)
What are the biggest mistakes to avoid?

I am itching to start piping around change data capture Debezium logs so tell me now before I inflict a horror on my co-workers.

Re:PranaDB – A distributed streaming database, designed to b... by guywhocodes on Saturday April 30, 2022 @12:49AM (#31213427)
Outbox pattern is nice, inbox is more questionable. Depending on size of org you might want to solve that exactly once.
Re:PranaDB – A distributed streaming database, designed to b... by higeorge13 on Saturday April 30, 2022 @04:27AM (#31214339)
Debezium should be fine as you ingest wal logs to kafka. Most problems derive when you push data both to kafka and postgres and assume that they are going to be the same. They won’t.
Re:PranaDB – A distributed streaming database, designed to b... by adtac on Saturday April 30, 2022 @12:02AM (#31213247)
>man-millennia

that's a new one