Last active
December 15, 2015 00:09
-
-
Save steveklabnik/5171193 to your computer and use it in GitHub Desktop.
Resque roadmap
This file contains 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
| Rescue 1.x | |
| ---------- | |
| - Pretty good but has bugs | |
| - used by a LOT of people. (30k) | |
| - fixing issues that are open | |
| - 1.23.x will be the end | |
| - just bugfixes | |
| Resque 2.0 | |
| ---------- | |
| - opportunity for change | |
| - can't totally break everything | |
| - Rails 4 job queue api got moved to 4.1 | |
| - lots of refactoring (remove singletons) | |
| - not break plugins as much as possible (possibly expose new APIs) | |
| - new site/branding publically and resque-web | |
| - Serialization? JSON vs. Marshal | |
| - Consumers? | |
| FEATURES | |
| -------- | |
| all optional | |
| 1. binary using Thor (eg resque work rather than rake rescue:work) | |
| 2. Durable queues | |
| 3. heartbeats for workers | |
| 4. threaded job model | |
| 5. splitting out resque-web (https://github.com/livingsocial/resque-web) | |
| 6. rails-ifying resque-web | |
| 7. failure API improvements | |
| 8. JRuby or RBX | |
| 9. Config API (like .rspec, .resque) | |
| 10. Rails Queue API? |
resque-web is just the UI component of resque, I don't think it matters which web framework you use for that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
for those of us who use rescue intensively on projects that are not rails, rails-ifying resque-web or any part of resque is a bad thing.