iggy
iggy copied to clipboard
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://docs.rs/tokio-util/0.7.4/tokio_util/codec/index.html mainly for `Messages`
As described [here](https://docs.confluent.io/kafka/design/log_compaction.html), log compaction could be a new kind of retention policy, allowing to override (and even delete for the null/empty payload) the old values for the same ID,...
Perhaps trying to use write_vectored instead of write_all to reduce memory copying and system call overhead can improve the performance.
- add bot issue raising when something goes wrong - improve comments in yml
Currently, if something goes wrong when command is handled, we have this print (this is example): `2024-01-22T10:04:18.487936Z ERROR server::binary::command: Command was not handled successfully, session: client ID: 4248576011, user ID:...
So we can run `iggy` on microcontrollers like `ESP32` Just TCP for start, use smoltcp, no async, can be blocking, place it in new folder like `thin-sdk` or `no_std_sdk` in...