Ross ROSS = Recommend OSS · open-source software intelligence for agents

apache/iggy

Apache Iggy: Hyper-Efficient Message Streaming at Laser Speed observed · 2026-08-28

github.com/apache/iggy · homepage · Rust · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

86/100

  • Activity 99
  • Release rhythm 68
  • Longevity 90
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 1
  • age_days: 1264
  • days_rel: 133
  • days_push: 7
  • n_releases_24m: 70

Full methodology

Adoption not part of the score

4545 stars · 384 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Apache Iggy is a high-performance, persistent message streaming platform written in Rust, supporting TCP, QUIC, HTTP, and WebSocket transports with sub-millisecond latency and millions of messages per second throughput. It includes a server with built-in VSR clustering, SDKs for 8 languages, a CLI, Web UI, connector runtime, and an MCP server for LLM integration.

Use cases

  • stream millions of events per second with low latency
  • replace Kafka with a lightweight single-binary message broker
  • build event-driven microservices with consumer groups and offsets
  • ingest data from PostgreSQL or Elasticsearch into streams via connectors
  • manage streams and topics from a terminal or web dashboard
  • let LLM agents inspect and manage message streams via MCP
  • run a fault-tolerant replicated message cluster with VSR consensus

When to choose

  • you need ultra-low-latency, high-throughput persistent message streaming
  • you want a single ~20 MB dependency-free binary instead of JVM-based Kafka
  • you need multiple transport options (TCP, QUIC, HTTP, WebSocket) and many language SDKs
  • you want built-in clustering with Viewstamped Replication and deterministic simulation testing

When to avoid

  • you need battle-tested 1.0 production guarantees - Iggy has not reached a 1.0 release yet
  • you rely on the Kafka ecosystem and wire-compatible clients - the Kafka gateway is still in development
  • you need a mature connector ecosystem comparable to Kafka Connect
  • you require features like exactly-once transactional semantics across external systems

Facets

service · maturity active

message-queue streaming http-server rpc cli mcp etl microservices backend developer-tools self-hosted windows rust cross-platform self-hosted message-streaming quic tcp websocket io-uring thread-per-core vsr-consensus kafka-alternative event-streaming connectors web-ui sdk messaging real-time linux macos docker

10 sources

Member repositories

RepositoryRoleHealth v2
apache/iggymain86

For agents

markdown · JSON · MCP: product_card(name="apache/iggy")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem