[ANNOUNCE] Apache Iggy version 0.9.0 released

[Hubert Gruszecki <h....@gmail.com>]

Hello Everyone,

Apache Iggy 0.9.0 is released. This is the first release as a top-level
project of the
Apache Software Foundation, after graduation from the Incubator on
2026-08-19.

Apache Iggy is a high-performance, persistent message streaming platform
written in Rust.
It uses a next-generation io_uring, thread-per-core, shared-nothing
architecture for
ultra-low latency and throughput of millions of messages per second. It
supports QUIC, TCP,
WebSocket, and HTTP transports. Ecosystem integrations include Iceberg,
Elasticsearch, and
Flink. SDKs cover Rust, C++, C#, Java, Node.js, Python, Go, and PHP.

The 0.9.0 release is the largest one so far - 604 pull requests since
0.8.0.  For more details
see the release blog post which will be published on monday 21st of
September
2026 in https://iggy.apache.org/blogs

Built-in replication based on Viewstamped Replication lands in the server.
A cluster
bootstraps replicas, changes views without losing committed operations,
transfers state,
repairs a rejoining replica, and keeps one consensus group per partition.
Client
sessions resume across restarts. The replica plane is authenticated with a
PSK and
BLAKE3 handshake, optionally over TLS 1.3. Single-node deployment stays the
default, and
the [cluster] configuration section opts in.
A new binary wire protocol is shared by every SDK and built around a fixed
VSR
request and reply header. A protocol version handshake at login rejects
incompatible
clients.
The next-generation server is now the Apache Iggy server: thread-per-core,
io_uring,
and compio. All transports remain: TCP with TLS, QUIC, WebSocket, and HTTP.
A
deterministic simulator with seed-based workload fuzzing and consensus
oracles exercises
it, together with Miri checks in CI.
SDK parity improved across the board. The PHP SDK is new. The C++ SDK
gained messaging,
system, consumer group, and topic APIs. The Python SDK closed most API
gaps, and the Go
SDK added context.Context support and structured logging.
Six new sink connectors: ClickHouse, Delta Lake, S3, Apache Doris,
SurrealDB, and
Meilisearch. The InfluxDB v2 and v3 source and sink were reworked, and Avro
payload
support arrived.
Performance and operations work covers single-pass batch checksums, a
per-partition
LRU for sealed segment handles, zero-copy user-header decoding, CPU
affinity and cgroup
awareness, advertised address selectors for NAT and Kubernetes, and a
systemd watchdog.
The same repository releases the tooling and the SDKs from one source tree:

Rust SDK 0.11.0, CLI 0.14.0, Connectors runtime 0.5.0
MCP server 0.5.0, Web UI 0.4.0, Bench Dashboard 0.8.0
Python 0.9.0, Node.js 0.10.0, Java 0.9.0, C# 0.9.0, Go v0.9.0
Before you upgrade, note the breaking changes.

A 0.8.x client cannot talk to a 0.9.0 server, and the reverse holds too.
Move the server
and the SDKs together. The server configuration surface changed, so review
config.toml.
The on-disk format changed and there is no migration of 0.8.x data
directories. Until
1.0.0, an upgrade starts from a fresh data directory.

We thank every contributor to this release, and the wider Apache Iggy
community, for the
work that made it possible.

Artifacts are available on the Downloads page:
https://iggy.apache.org/downloads

Release Notes:
https://github.com/apache/iggy/releases/tag/server-0.9.0

We are eager to expand our community and extend an invitation to new
contributors. We
genuinely welcome the opportunity to collaborate with individuals who share
our passion
and expertise.

Website: https://iggy.apache.org
Repository: https://github.com/apache/iggy
Discussions: https://github.com/apache/iggy/discussions
Issue tracker: https://github.com/apache/iggy/issues
Mailing list: https://lists.apache.org/list.html?dev@iggy.apache.org
Discord channel: https://discord.gg/apache-iggy
Blogs: https://iggy.apache.org/blogs/

We care so deeply about performance and efficiency that benchmarks are a
first-class
citizen for us. Read more about our approach to benchmarks at
https://iggy.apache.org/blogs/2025/02/17/transparent-benchmarks. Community
published
benchmarks are uploaded to https://benchmarks.iggy.apache.org

Best,
Apache Iggy Community