luckyframework / luckyframework/lucky
Implement a background job shard
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 2.7k
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
I'm converting what used to be a 1.0 roadmap note into an issue so that we can have a bit more discussion but still track it on the Roadmap board. I don't think you can link discussions to projects, but we can always convert this to a discussion if it gets too "busy".
Paul linked a gist showing how we might accomplish something sort of similar to ActiveJob in Rails, where there's a common API you can "hook into" easily:
https://gist.github.com/paulcsmith/7ee1bd36d4738518f779951239226537
That said, I wonder if this is really something we need for a 1.0 release, or if we could just rely on something like Sidekiq or Mosquito more heavily with tutorials/community content.
My experience is that while yes, ActiveJob does have its uses, a high-performing job queue like Sidekiq implements its own way of doing things and recommends against using the ActiveJob interface.
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 reading the linked gist and the discussion about an ActiveJob-like API, then compare the stated tradeoffs with Sidekiq and Mosquito. The issue does not identify files, tests, an entry point, or settled acceptance criteria; scope and whether this belongs in the 1.0 release must be decided before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100