Most net stars, last 30 days
google-ai-edge/mediapipeCross-platform, customizable ML solutions for live and streaming media.
+402
48% of the net stars of this Tag
Tags / Data pipelines and messaging /
An engine or library that computes results continuously over event streams, such as Flink; not the event log itself.
The 37repositories with this Tag gained +839 net stars in the last 30 days, 11% less than the 30 days before.
0 created in the last 90 days · 11 published a release in the last 30 days · 269K stars in total
Oct 5, 2026Nov 3, 2026
Most net stars, last 30 days
google-ai-edge/mediapipeCross-platform, customizable ML solutions for live and streaming media.
+402
48% of the net stars of this Tag
Largest Pace, last 30 days
No other repository gained 2 or more times the net stars of the 30 days before.
Most stars, created in the last 90 days
No other repository with this Tag was created in the last 90 days.
Net stars gained each week. The repositories that gained the most have their own color.
google-ai-edge/mediapipe gained 39% of the net stars of this Tag in the last 13 weeks.
37 repositories with this Tag. Select a column name to change the order.
| # | Repository | Stars | Gained, 30 days | Pace | |
|---|---|---|---|---|---|
| 1 | google-ai-edge/mediapipe Cross-platform, customizable ML solutions for live and streaming media. | 38K | +402 | 1.1× | |
| 2 | apache/flink Apache Flink | 26K | +86 | – | |
| 3 | risingwavelabs/risingwave Event streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale. | 9.4K | +45 | – | |
| 4 | ThreeDotsLabs/watermill Building event-driven applications the easy way in Go. | 9.9K | +38 | – | |
| 5 | apache/beam Apache Beam is a unified programming model for Batch and Streaming data processing. | 8.7K | +32 | – | |
| 6 | ag2ai/faststream Asynchronous Python framework for event-driven services. A thin client for Kafka, RabbitMQ, NATS, Redis and MQTT with full access to native broker features, plus AsyncAPI docs, in-memory tests and observability out of the box. | 5.4K | +32 | – | |
| 7 | ArroyoSystems/arroyo Distributed stream processing engine in Rust | 5.1K | +32 | – | |
| 8 | hazelcast/hazelcast Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights. | 6.6K | +22 | – | |
| 9 | redpanda-data/connect Fancy stream processing made operationally mundane | 8.8K | +21 | – | |
| 10 | timeplus-io/proton The fastest unified streaming SQL Engine in a single C++ binary. ⚡ Millisecond latency. 100+ GB/s throughput. Continuously compute stateful context from streams, logs, metrics, events, and CDC. | 2.3K | +19 | – | |
| 11 | MaterializeInc/materialize The live data layer for apps and AI agents. Create up-to-the-second views into your business, just using SQL | 6.4K | +18 | – | |
| 12 | bytewax/bytewax Python Stream Processing | 2.1K | +17 | – | |
| 13 | apache/incubator-kie Apache KIE (Knowledge Is Everything) is the home of Drools, OptaPlanner, jBPM, and Kogito. | 6.3K | +10 | – | |
| 14 | lf-edge/ekuiper Lightweight data stream processing engine for IoT edge | 1.7K | +10 | – | |
| 15 | dotnet/reactive The Reactive Extensions for .NET | 7.2K | +8 | – | |
| 16 | fluvio-community/fluvio 🦀 event stream processing for developers to collect and transform data in motion to power responsive data intensive applications. | 5.3K | +8 | – | |
| 17 | elixir-broadway/broadway Concurrent and multi-stage data ingestion and data processing with Elixir | 2.7K | +8 | – | |
| 18 | numaproj/numaflow Kubernetes-native platform to run massively parallel data/streaming jobs | 2.8K | +7 | – | |
| 19 | quixio/quix-streams Python Streaming DataFrames for Kafka | 1.6K | +7 | – | |
| 20 | apache/storm Apache Storm | 6.7K | +5 | – |
Net stars of the last 30 days are 2 or more times those of the 30 days before.
No repository with this Tag meets this rule now.
Net stars of the last 30 days are 50% or less of those of the 30 days before.
Created on GitHub in the last 90 days.
No repository with this Tag meets this rule now.
Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.
The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.
All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.
For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.
The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.
The chart at the top adds up the net stars of all the repositories with the Tag. The darker area is the part from the Seed Dataset; the rest is from rising Admissions. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time. The repositories of the Seed Dataset are a set that does not change.
The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.