←back to thread

Show HN: Building WebSocket in Apache Iggy with Io_uring and Completion Based IO

(iggy.apache.org)
29 points spetz | 1 comments | 17 Nov 25 18:00 UTC | HN request time: 0.199s | source
Show context
swiftcoder ◴[17 Nov 25 20:34 UTC] No.45957968[source]▶
Having worked on a number of message brokers, but not really fucked with append-only log streams, what's the actually selling point here?

Feels like the simplicity wins are made by only solving one half of the problem space (only writes), and it introduces new problems of its own (like how do we truncate the append-only log once readers are done with it?)

replies(1): >>45958593 #
1. spetz ◴[17 Nov 25 21:34 UTC] No.45958593[source]▶
There's a core difference between the message queue and the stream, and one of them is that the append-only log acts as a simple database from which multiple independent consumers can read records at the same time; hence, you don't truncate the append-only log unless specified in its settings via a particular cleanup policy (e.g. based on message expiry or its allowed size).