apache/iggy

Apache Iggy: Hyper-Efficient Message Streaming at Laser Speed

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 14th, 2026
Created on March 18th, 2023
Open Issues & Pull Requests: 203 (+0)
GitHub issues: Enabled
Number of forks: 442
Total Stargazers: 4,913 (+0)
Total Subscribers: 33 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.7 hours
Mean response time: 46.4 days
90th percentile: 96.6 days
Tracked items: 776

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 5% of issues opened in the past year have never received a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "rust" is answered fastest, typically in under an hour, while "java" waits about 6 weeks. 11% of tracked open issues have had no activity in three months. 66% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 155
New in 7 days: 21
Closed in 7 days: 16
Avg open age: 118 days
Stale 30+ days: 55
Stale 90+ days: 19

Recent activity

Opened in 7 days: 13
Closed in 7 days: 10
Comments in 7 days: 10
Events in 7 days: 50

Top labels

  • bug (219)
  • good first issue (133)
  • connectors (91)
  • server (79)
  • enhancement (65)
  • sdk (46)
  • rust (44)
  • test (44)

Detailed Description

Apache Iggy is a message streaming platform built in Rust that prioritizes high throughput and low latency for distributed systems.

The platform addresses the need for efficient message streaming by implementing a broker-based architecture that handles pub-sub and message queue patterns. It supports multiple transport protocols including TCP and QUIC, allowing clients to choose based on their performance requirements. The design emphasizes minimizing overhead and maximizing throughput, making it suitable for scenarios where message delivery speed and system efficiency are critical.

Teams evaluating Iggy should consider it for applications requiring high-performance event streaming, real-time data pipelines, or distributed messaging where latency and resource consumption matter significantly. The Rust implementation provides memory safety and performance characteristics that appeal to infrastructure-focused projects. The platform is particularly relevant for organizations already invested in Rust ecosystems or those building systems where traditional message brokers may introduce unacceptable overhead.

The project maintains active development with regular commits addressing core functionality and protocol improvements. The codebase shows ongoing refinement of the streaming engine and transport layer implementations. Documentation and community engagement through multiple channels indicate sustained effort to support adoption and gather feedback from users.