

Apache Iggy, a Rust-based message streaming project, published server version 0.10.0 on November 7. The release includes work on a Kafka bridge, client libraries and operational fixes across the streaming stack.
What developers can inspect
The published change list describes mapping between Kafka records and Iggy messages, work on offsets and a SASL/PLAIN authentication addition to the gateway. It also lists C++ client improvements, Swift SDK scaffolding and fixes in partition handling. These individual changes should not be read as a promise of complete Kafka compatibility: consult the release notes and gateway documentation for the precise implemented scope.
For developers building services that exchange events, a bridge can reduce integration friction, but message semantics, consumer behavior, security and failure recovery still need testing in the target deployment. We have not installed the release or measured throughput.
Start at the source
The project repository is Apache-2.0 licensed. Read the version-specific configuration and migration guidance before changing an existing service. Our view is that the most valuable open infrastructure is inspectable and recoverable under failure, not just fast in a best-case benchmark.
EXPLORE THE SOURCE
Projects in this story
GitHub repositories
- apache/iggy ↗View project details
Original reporting and analysis based on the linked primary sources. We did not independently test the products or benchmark the models.




