Decouple Dash & Celery
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
I use Dash in combination with Celery to deal with long-running background callbacks. Within these callbacks, data is being retrieved using Spark. Since I have to run the frontend (Dash) and the backend (Spark) in separate containers anyway, I'd like to decouple the dependencies. The frontend does not need a full Spark installation (quite big!) and the backend does not need any web-related dependencies.
In other projects, I followed the concept outlined in decoupled-celery-example. However, due to the very integrated nature of Dash's callback-decorators, I struggle to decouple the workers.
Is this somehow possible?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Dash's background-callback documentation and the linked decoupled-celery-example, then trace how callback decorators connect the frontend to Celery workers. The issue does not identify files or tests; done would require a decided, supported approach for separating Dash/web dependencies from Spark worker dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, spark
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100