Add FastStream

[lesnik512]

https://github.com/lesnik512/awesome-faststream#readme

FastStream is an asynchronous Python framework for building event-driven services on top of Kafka, RabbitMQ, NATS, and Redis. It gives you a single API across those brokers plus typed messages, dependency injection, testing helpers, and generated AsyncAPI docs.

Over the past year a real ecosystem has grown around it - broker adapters (IBM MQ, KubeMQ, STOMP), DI integrations, reliability patterns like a transactional outbox and distributed timers, observability tooling, and starter templates - but it is scattered across many separate repos and orgs. I maintain a number of these projects myself, so I put this list together to collect the ones actually worth knowing and keep it curated rather than exhaustive. It fits Back-End Development next to FastAPI, which FastStream is closely modeled on.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

• Fully AI-generated pull requests are not accepted.
• Don't open a Draft / WIP pull request while you work on the guidelines.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 4 other open pull requests. Reviewed: Add Analysis #4350, Add AI Search Readiness #4345, Add FilamentPHP #3564, Add BYOC #3901.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List.
• Your entry here includes a short description of the project/theme of the list.
• Your entry is added at the bottom of the appropriate category.
• The title of your entry is title-cased and the URL to your list ends in #readme.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
• Is not AI-generated.
• Run awesome-lint on your list and fix the reported issues.
• The default branch is named main, not master.
• Includes a succinct description of the project/theme at the top of the readme.
• It's the result of hard work and the best I could possibly produce.
• The repo name of the list is in lowercase slug format: awesome-faststream.
• The heading title of the list is in title case: # Awesome FastStream.
• Non-generated Markdown file in a GitHub repo.
• The repo has awesome-list & awesome as GitHub topics.
• Not a duplicate. I searched for existing submissions.
• Only has awesome items.
• Does not contain items that are unmaintained, archived, deprecated, or missing docs.
• Includes a project logo/illustration.
• Entries have a description.
• Includes the Awesome badge.
• Has a Table of Contents section named Contents as the first section.
• Has an appropriate license (CC0-1.0).
• Has contribution guidelines in contributing.md.
• Has consistent formatting and proper spelling/grammar.
• Does not use hard-wrapping.
• Does not include a CI badge.
• Does not include an Inspired by awesome-foo link at the top of the readme.

[lesnik512]

Reviewed 4 other open PRs as required:

• Add Analysis #4350 - description guideline issues in the readme
• Add AI Search Readiness #4345 - editorializing intro vs objective description
• Add FilamentPHP #3564 - entry casing, CI badge in heading, license detection
• Add BYOC #3901 - entry description repeats the list name

[lesnik512]

unicorn

[tariqkhalil2003-lgtm]

Ok

[GeekCornerGH]

The PR seems to follow the guidelines

[mxuexxmy]

Reviewed the entry and awesome-faststream.

Looks good overall. Title/format/#readme URL are correct, entry is at the bottom of Back-End Development, topics/CC0/CONTRIBUTING.md/Awesome badge/Contents all look in order. The list is focused and curated rather than a dump.

Nits:

• The proposed description is accurate but a bit long next to neighboring entries; something like Asynchronous Python framework for event-driven services over Kafka, RabbitMQ, NATS, and Redis. would still be objective and a bit tighter.
• Placement at the category bottom is correct per guidelines; thematically it also sits well near FastAPI-related tooling if maintainers ever regroup.

No blockers spotted from my side.

[dofaromg]

我是root為何串改任務根產品名稱

[yboulaamane]

I reviewed the catalog entry and the linked list in detail. The entry is correctly placed at the bottom of Back-End Development, and the list has the required badge, Contents section, CC0 license, and contribution guide. I also checked all 17 GitHub repositories linked from the README: they are currently public and none is archived.

Two improvements remain:

• The file starts with <!-- lint disable double-link -->, which disables duplicate-link checking for the entire README merely because the FastStream repository is linked in both the introduction and Official Resources. Please avoid the duplicate (for example, leave the repository link in Official Resources and link the introductory text to the documentation/site) and remove the global lint suppression. Keeping the rule enabled will catch accidental duplicate entries later.
• The PR explains that you maintain several projects in the list, but the README does not disclose which entries those are. Because this is a curated recommendation list, please add a short Footnotes disclosure identifying the curator-maintained projects. Keep that section at the bottom and out of Contents, as required by the guidelines.

The scope is focused and the linked projects appear active; these changes would make the curation and linting more transparent.

[lesnik512]

@yboulaamane Thanks for actually opening the repos - both points addressed in lesnik512/awesome-faststream@4440c9b.

On the lint suppression: you were right that it shouldn't be there. Your suggested fix wouldn't have worked, though - linking the intro to the documentation site just moves the duplicate, since https://faststream.ag2.ai is already the Documentation entry in Official Resources. Instead I left "FastStream" unlinked in the intro paragraph; the logo above it still links to the site, and the repo link stays in Official Resources. <!-- lint disable double-link --> is gone and awesome-lint passes clean, so the rule is now active for the whole list.

On disclosure: I couldn't find a guideline requiring it, but it's a fair ask for a curated list, so I added a Footnotes section at the bottom, outside Contents. It names the six entries I maintain (the modern-python ones) and separately notes the two I only contribute to, so the distinction isn't blurred.