arroyosystems/arroyo

Distributed stream processing engine in Rust

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 13th, 2026
Created on March 31st, 2023
Open Issues & Pull Requests: 127 (+0)
GitHub issues: Enabled
Number of forks: 378
Total Stargazers: 5,039 (+0)
Total Subscribers: 49 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.8 days
Mean response time: 45.5 days
90th percentile: 111.8 days
Tracked items: 84

Most active contributors

Sign in to see contributor activity.

How this project is maintained

97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 70
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 460 days
Stale 30+ days: 66
Stale 90+ days: 62

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (17)
  • connector (12)
  • bug (11)
  • good first issue (3)
  • sql (3)
  • runtime-panic (2)
  • ux (1)

Detailed Description

Arroyo is a distributed stream processing engine written in Rust that executes stateful computations on bounded and unbounded data streams with subsecond latency.

The tool addresses the need to perform complex analytical queries on high-volume real-time data. It uses SQL as a first-class interface, allowing users to define streaming pipelines declaratively rather than through imperative code. The engine implements the Dataflow model for time-oriented stream processing, supporting stateful operations like windowing and joins, and provides state checkpointing to enable fault tolerance and recovery.

Arroyo suits teams building real-time analytics, fraud detection, security monitoring, or ML feature generation pipelines who want to avoid the operational complexity of traditional streaming systems. It targets users who may not be streaming experts, emphasizing clean separation between pipeline APIs and internal implementation details. The README positions it against Apache Flink, Spark Streaming, and Kafka Streams, highlighting three distinguishing points: serverless-first design for cloud environments with automatic scaling and rescheduling, SQL as a high-performance first-class concern rather than an add-on, and a focus on accessibility for non-experts over low-level control.

The project maintains active development with regular commits and passing continuous integration. Pull requests are welcomed according to the repository guidelines.