Add Dispytch to Asynchronous Programming section #2733
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dajcu12
approved these changes
Jul 12, 2025
potosino163
reviewed
Jul 22, 2025
What do you mean? |
balrambheel924-spec
approved these changes
Jul 24, 2025
princeaden1
approved these changes
Aug 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.