openedx / openedx/openedx-events
[Consumer] [Discovery] Treat consumer message processing like a Django request
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 33
- Avg merge
- 14h 37m
- Merged PRs (30d)
- 4
Description
Is there a more general solution possible in Django for calling Django's typical before-request and after-request code when processing each message? This might provide an alternate solution to https://github.com/edx/edx-arch-experiments/issues/158.
Maybe this isn't a high-priority, but I wonder what issues may be lurking that we just wouldn't be aware of.
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 by reviewing Django's typical before-request and after-request processing alongside the consumer message-processing path. Compare the possible approach with the alternate solution referenced in issue #158; done should mean a defined, general solution or a documented explanation of why it is not feasible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100