github-starred/awesome-python
2
0
Fork 0
mirror of https://github.com/vinta/awesome-python.git synced 2026-05-07 14:17:36 -05:00
Code Issues 464 Packages Projects Releases Wiki Activity

[PR #3079] [MERGED] docs(message-brokers): add FastStream and Message Brokers category #11354

New Issue
Closed
opened 2026-04-24 06:08:01 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-24 06:08:01 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/vinta/awesome-python/pull/3079
Author: @vvlrff
Created: 4/21/2026
Status: ✅ Merged
Merged: 4/24/2026
Merged by: @JinyangWang27

Base: master ← Head: add-faststream

📝 Commits (3)

  • 4a334d9 docs(message-brokers): add FastStream and Message Brokers category
  • ead4794 Merge branch 'master' into add-faststream
  • 427dfc0 Rename Message Brokers to Messaging

📊 Changes

1 file changed (+7 additions, -0 deletions)

View changed files

📝 README.md (+7 -0)

📄 Description

Project

FastStream

Checklist

  • One project per PR
  • PR title format: Add project-name
  • Entry format: - [project-name](url) - Description ending with period.
  • Description is concise and short

Why This Project Is Awesome

Which criterion does it meet? (pick one)

  • Industry Standard - The go-to tool for a specific use case
  • Rising Star - 5000+ stars in < 2 years, significant adoption
  • Hidden Gem - Exceptional quality, solves niche problems elegantly

Explain:

FastStream is the de-facto Python framework for building event-driven services on top of message brokers. It has 5.1k+ GitHub stars, active releases, production adoption, and a unified API across Apache Kafka, RabbitMQ, NATS, and Redis Streams. It brings the FastAPI developer experience (typed handlers powered by Pydantic, dependency injection, auto-generated AsyncAPI docs) to async messaging, which historically required hand-written broker-specific clients.

The README currently has no category for message brokers / event streaming at all — this PR fills that gap by introducing a new Message Brokers section and placing FastStream as its first entry.

Note: a previous PR (#2519, closed) proposed FastStream in 2023 when it only supported Kafka and RabbitMQ and described itself very briefly. Since then the project has grown substantially (5.1k+ stars, NATS and Redis support added, stable 0.6.x line, integrations with FastAPI), which justifies revisiting it.

How It Differs

The existing README entries under Task Queues (celery, dramatiq, huey, rq) solve a different problem — dispatching and executing background jobs from within an application. FastStream targets a distinct use case: building long-running consumer/producer services that participate in event-driven architectures over real brokers (Kafka topics, RabbitMQ queues/exchanges, NATS subjects, Redis streams), with schema validation, lifespan management, and AsyncAPI documentation as first-class concerns. There is currently no entry in the list that covers this.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/vinta/awesome-python/pull/3079 **Author:** [@vvlrff](https://github.com/vvlrff) **Created:** 4/21/2026 **Status:** ✅ Merged **Merged:** 4/24/2026 **Merged by:** [@JinyangWang27](https://github.com/JinyangWang27) **Base:** `master` ← **Head:** `add-faststream` --- ### 📝 Commits (3) - [`4a334d9`](https://github.com/vinta/awesome-python/commit/4a334d9cda5345069af076f17f8f887d652b61b8) docs(message-brokers): add FastStream and Message Brokers category - [`ead4794`](https://github.com/vinta/awesome-python/commit/ead4794fc985220fdde2cefec6f2b2007278c812) Merge branch 'master' into add-faststream - [`427dfc0`](https://github.com/vinta/awesome-python/commit/427dfc000310d618ecac57bafce66b62a134961e) Rename Message Brokers to Messaging ### 📊 Changes **1 file changed** (+7 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+7 -0) </details> ### 📄 Description ## Project [FastStream](https://github.com/ag2ai/faststream) ## Checklist - [x] One project per PR - [x] PR title format: `Add project-name` - [x] Entry format: `- [project-name](url) - Description ending with period.` - [x] Description is concise and short ## Why This Project Is Awesome Which criterion does it meet? (pick one) - [x] **Industry Standard** - The go-to tool for a specific use case - [x] **Rising Star** - 5000+ stars in < 2 years, significant adoption - [ ] **Hidden Gem** - Exceptional quality, solves niche problems elegantly Explain: FastStream is the de-facto Python framework for building event-driven services on top of message brokers. It has 5.1k+ GitHub stars, active releases, production adoption, and a unified API across Apache Kafka, RabbitMQ, NATS, and Redis Streams. It brings the FastAPI developer experience (typed handlers powered by Pydantic, dependency injection, auto-generated AsyncAPI docs) to async messaging, which historically required hand-written broker-specific clients. The README currently has no category for message brokers / event streaming at all — this PR fills that gap by introducing a new **Message Brokers** section and placing FastStream as its first entry. Note: a previous PR ([#2519](https://github.com/vinta/awesome-python/pull/2519), closed) proposed FastStream in 2023 when it only supported Kafka and RabbitMQ and described itself very briefly. Since then the project has grown substantially (5.1k+ stars, NATS and Redis support added, stable 0.6.x line, integrations with FastAPI), which justifies revisiting it. ## How It Differs The existing README entries under **Task Queues** (`celery`, `dramatiq`, `huey`, `rq`) solve a different problem — dispatching and executing background jobs from within an application. FastStream targets a distinct use case: building long-running consumer/producer services that participate in event-driven architectures over real brokers (Kafka topics, RabbitMQ queues/exchanges, NATS subjects, Redis streams), with schema validation, lifespan management, and AsyncAPI documentation as first-class concerns. There is currently no entry in the list that covers this. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-24 06:08:02 -05:00
GiteaMirror changed title from [PR #3079] docs(message-brokers): add FastStream and Message Brokers category to [PR #3079] [MERGED] docs(message-brokers): add FastStream and Message Brokers category 2026-04-27 03:08:29 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-python#11354
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?