Skip to content

rutomq v0.1.0 — public preview

Choose a tag to compare

View all tags
@SamuelSupe SamuelSupe released this 30 Jul 02:53
· 1 commit to main since this release
v0.1.0
b538c3c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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.

Assets 9
Loading