rutomq v0.1.1 — resource-boundary hardening

rutomq v0.1.1 is a resource-boundary hardening release built on the v0.1.0 public-preview compatibility envelope.

Highlights

• Bounds Kafka and admin connections, request sizes, response buffers, and write lifetimes.
• Reserves encoded-response memory before allocation and retains the permit through slow network writes.
• Paginates or batches garbage collection, retention, expired-transaction cleanup, and group observability queries.
• Prevents object-write coordination keys from accumulating after writes complete.
• Rejects invalid production storage and listen configuration at startup.
• Exposes the new operational limits through environment and Helm configuration.

Validation

• Protocol tests: 7 passed.
• Control tests: 166 passed.
• PostgreSQL boundary tests: 13 passed against a temporary PostgreSQL instance.
• Response-budget regression tests passed.
• Workspace check and Clippy with all features and targets passed.
• Helm lint passed.

See the compatibility matrix and dated v0.1.0 acceptance result before production evaluation.

rutomq v0.1.0 — public preview

rutomq v0.1.0 — public preview

v0.1.0 is the first public rutomq release: a Rust-based, Kafka-compatible
message queue with stateless Agents, PostgreSQL coordination, and immutable
S3-compatible object storage.

Highlights

• No Agent-local WAL, partition data, PVC, or recovery journal.
• Produce acknowledgement occurs only after object storage and PostgreSQL both
  commit successfully.
• Kafka 4.3 generated wire baseline with 74 API keys in the advertised
  compatibility surface.
• Idempotent production, transactions, read_committed, consumer groups,
  share groups, Kafka Streams groups, retention, and compaction.
• Kafka Java, librdkafka, franz-go, Flink 2.2.1, and Kafka Streams 4.2
  acceptance.
• TLS, SCRAM-SHA-256/512, delegation tokens, ACLs, quotas, health probes, and
  Prometheus metrics.
• Docker Compose development stack and a stateless Helm deployment.

Validation checkpoint

The release checkpoint passed formatting, strict Clippy, workspace tests,
release builds, fresh PostgreSQL integrations, OpenDAL/MinIO multipart and
range tests, native clients, Flink, Kafka Streams, security, multi-Agent
failure scenarios, retention recovery, and Kubernetes rollout/scaling in
OrbStack.

Read the exact evidence and boundaries in the
compatibility result.
The API matrix
is the source of truth for advertised request versions and behavior.

Important boundaries

This is a public preview, not a claim of complete semantic parity with every
Apache Kafka deployment.

• Non-empty online classic/consumer group protocol migration is not included.
• The service exposes one virtual broker/controller/ISR topology; physical
  replica logs, follower reads, local log directories, and real KRaft state are
  not invented.
• PostgreSQL and S3-compatible storage are required for durable progress.
• Cross-region replication, Schema Registry, Kafka Connect management, a
  Kubernetes Operator, and multi-virtual-cluster isolation are outside this
  release.

Release assets

GitHub provides source archives automatically. The release workflow also
publishes:

• a Linux x86-64 rutomq binary archive;
• the rutomq-0.1.0.tgz Helm chart;
• SHA256SUMS;
• GitHub artifact attestations for the packaged binary and chart.

Getting started

git clone --branch v0.1.0 https://github.com/SamuelSupe/rutomq.git
cd rutomq
docker compose -f deploy/compose.dev.yml up --build -d
curl --fail http://127.0.0.1:8080/health/ready

See the quick-start guide
for Produce, Consume, metrics, and cleanup commands.