mirror of
https://github.com/vinta/awesome-python.git
synced 2026-03-22 14:12:18 -05:00
[PR #2733] Add Dispytch to Asynchronous Programming section #2046
Reference in New Issue
Block a user
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?
📋 Pull Request Information
Original PR: https://github.com/vinta/awesome-python/pull/2733
Author: @e1-m
Created: 7/10/2025
Status: 🔄 Open
Base:
master← Head:master📝 Commits (1)
3b1b6aaUpdate README.md📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
What is this Python project?
Dispytch is a lightweight, async-first Python framework for event-handling. It’s designed to streamline the development of clean and testable event-driven services.
Features
Async-first core – built for modern Python I/O
FastAPI-style dependency injection – clean, decoupled handlers
Backend-flexible – with Kafka and RabbitMQ out-of-the-box
Composable architecture – extend, override, or inject anything
Pydantic-based validation – event schemas are validated using pydantic
Built-in retry logic – configurable, resilient, no boilerplate
What's the difference between this Python project and similar ones?
vs Celery: Dispytch is not tied to task queues or background jobs. It treats events as first-class entities, not side tasks.
vs Faust: Faust is opinionated toward stream processing (à la Kafka). Dispytch is backend-agnostic and doesn’t assume streaming.
vs Nameko: Nameko is heavier, synchronous by default, and tied to RPC-style services. Dispytch is lean, async-first, and modular.
vs FastAPI: FastAPI is HTTP-centric. Dispytch is protocol-agnostic — it’s about event handling, not API routing.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.