iggy

There's an open PR to implement sink + source for MQTT https://github.com/apache/iggy/issues/3385 Also, since we've been asked about this a lot, there's a high chance, that we might implement MQTT Gateway, just like we currently do for Kafka (proxy on top, as a separate runtime).

Apache Iggy seems like a project with a lot of momentum: https://github.com/apache/iggy

There's also Iggy https://github.com/apache/iggy Never tried it, but looks promising

Thanks! Actually, the mentioned PR was just an internal merge; the one to the master branch is this one https://github.com/apache/iggy/pull/2299 which happened last week :) Sans-IO is for clients only, and we'd like to introduce it one day to SDK to support the different runtimes as well as the blocking, sync client.

Fun write-up. Good stuff, very nice contribution to to compio of compio-ws. Looks like the Iggy switched to thread-per-core compio back in July. https://github.com/apache/iggy/pull/1960 One thing I saw mentioned in the 0.5.0 release notes (which happened shortly after migrating to compio): trying to switch to a Sans-IO model design (but maybe just for clients?). It feels like there's similar ownership concerns that might arise, as seen here with the poll-vs-completion challenges faced here. A lot of good learnings to be had, as we go forth to faster better io, eager to keep tuning in & hearing more. Thanks for the write up! https://iggy.apache.org/blogs/2025/08/10/release-0.5.0/#what... https://www.firezone.dev/blog/sans-io

There's probably good advantages to a well tuned more bespoke multiplexing protocol toolkit… But it sure makes me crazy crazy sad that QUIC and HTTP3 are still rarefied technologies with little mainstream adoption. The hyperscalers all seem to have a library or two they've made… https://github.com/mmmarcos/awesome-quic?tab=readme-ov-file#... …but there's still no mainstream http3 that works well with a http framework of any kind that one can just use. Hyper's h3 kicks along slowly. Node.js has been beleaguered by openssl's endless beating around the bush reinventing how they want to do quic, ignoring input. But that's finally starting to move. https://github.com/hyperium/h3 https://github.com/nodejs/node/issues/57281 Muxio was able to define itself & an inpl pretty fast, and performance & usability are probably both medium or high. That e

> Iggy is the persistent message streaming platform written in Rust, supporting QUIC, TCP and HTTP transport protocols, capable of processing millions of messages per second. https://github.com/iggy-rs/iggy Looks neat. The SQLite of Kafka.