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.
Purpose of this task is to create test cases that will verify whether creating resources such as streams, topics, partitions leads to race conditions when propagating events to other shards.
This adds a Nix flake which provides: - hermetic development environment for linux & macos - overlay for Nix projects to import and use iggy binaries and libraries
Bumps [figment](https://github.com/SergioBenitez/Figment) from 0.10.18 to 0.10.19. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR by commenting `@dependabot rebase`. [//]: #...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
In order to support clustering in the future, the server should store the received commands in the form of a basic stream (append-only log) instead of a custom database with...
Like in `monoio` project 
Similar to the existing `DeletePartitions` command, we could introduce another kind of "administrative" request for deleting the segments. Given the specific Stream ID + Topic ID + Partition ID, the...
In `iggy-server` messages cache works in per partition manner. When partition object is created, and cache is enabled, it creates internal `SmartCache`object, which is essentially wrapper around `VecDeque`. In other...
Perhaps it should be possible to use crate https://docs.rs/rolling-file/latest/rolling_file/ instead of `tracing-appender`. The parameter itself is already in the config.