iggy
iggy copied to clipboard
iggy-rs
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.
So that there will `no less` info than currently. This is already done for topic: ```rust impl fmt::Display for Topic { fn fmt(&self, f: &mut fmt::Formatter
For example using https://github.com/near/near-memory-tracker We should be able to enable/disable this in runtime, so LD_PRELOAD is not an option.
The aim of this task is to change `iggy` folder to `sdk` and update README.md README.md should be updated with: - describe what's delivered via crates.io (maybe separate README.md for...
We want each open PR to have thread with all comments (not just open/closed PR) use https://github.com/inngest/olotl or something similiar
The aim of this issue is to create fuzz testcases that would bombard server with random data and check behavior. Server shouldn't ever crash. Assume auth is done. https://en.wikipedia.org/wiki/Fuzzing
Server is not logging enough in cold paths. Any invalid command, like create/update stream, topic, tbh anything that would not overflow the logs should be logged with appropriate severity (err/wrn)....
As in title. Protocol specs are somewhere in the docs.