You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Hubert Gruszecki <hg...@apache.org> on 2026/04/22 10:45:34 UTC
[ANNOUNCE] Apache Iggy (Incubating) 0.8.0 released
The Apache Iggy (Incubating) community is pleased to announce the
release of Apache Iggy (Incubating) 0.8.0.
Apache Iggy is a persistent message streaming platform written in
Rust, supporting QUIC, TCP, WebSocket and HTTP transport protocols,
capable of processing millions of messages per second with ultra low
latencies.
Release highlights:
- Clustering foundations: new `shard` crate with generic `IggyShard`
and shard router, a persistent WAL journal with recovery and
compaction for the metadata state machine, and a deterministic
PacketSimulator for distributed-system testing.
- Binary protocol refactor: dedicated `iggy_binary_protocol` crate
with zero-copy wire types for all commands, a sans-IO frame codec,
and a command dispatch table — consolidating serialization into a
single auditable path.
- Security hardening: user headers now encrypted alongside message
payload, credentials wrapped in `SecretString` to prevent leaks,
random JWT secrets generated when none are configured, and 15
Dependabot vulnerability alerts resolved.
- New connectors and SDK expansion: MongoDB, InfluxDB (sink + source),
and generic HTTP sink connectors; major Java SDK work (async API
parity, connection pooling, connection timeout); TCP/TLS support
across Go, Node, and C# SDKs; Bazel build infrastructure for C++.
Downloads:
https://iggy.apache.org/downloads/
Release notes:
https://github.com/apache/iggy/releases/tag/server-0.8.0
Release blog post:
https://iggy.apache.org/blogs/2026/04/22/release-0.8.0
To learn more about Iggy, please visit https://iggy.apache.org
We welcome feedback, bug reports and contributions.
=====
*Disclaimer:*
Apache Iggy is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation
is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily
a reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.
Thanks,
The Apache Iggy (Incubating) Team