[idea] uncouple drivers and executors
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.1k
- Forks
- 285
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
Maybe drivers should only deal with message sourcing and sinking and create new class definitions that are executors
That way one could implement more executors.
I have issue that I would like to use Db driver, but that currently forces me to use CLI executor (or as far as I can see everything is using CLI executor except sync)
but what If I wanted to create another type of executor? (currently on older one I created Threaded executor(Was based on controller))pthreads
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 tracing how the DB driver, CLI executor, and sync path are connected, then compare the earlier Threaded executor/controller approach mentioned in the issue. Done means drivers handle message sourcing and sinking independently from executors, while the DB driver can be used with an alternative executor such as a threaded one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100