anth-git opened a new issue, #4048: URL: https://github.com/apache/iggy/issues/4048
### Description Add an opt-in RAM-only storage backend for deployments where low latency and avoiding disk writes are more important than durability. In this mode, Iggy would keep messages, indexes, metadata, consumer offsets, and other runtime state entirely in memory. All state would be intentionally lost when the server process exits or the host restarts. Motivation: a high-throughput, low-latency message broker where: - Message loss after a server crash or restart is acceptable. - Writing messages to SSD provides no useful benefit. - Avoiding SSD wear is important. ### Affected area / component Iggy server ### Proposed solution _No response_ ### Alternatives considered _No response_ ### Contribution - [ ] I'm willing to submit a pull request to implement this feature ### Good first issue - [ ] I think this could be a good first issue for a new contributor -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
