• No additional infrastructure
DelayedJob is easy to get started
Slide 46
Slide 46 text
• No additional infrastructure
• ActiveRecord
DelayedJob is easy to get started
Slide 47
Slide 47 text
ActiveJob makes
swapping backends easy
Slide 48
Slide 48 text
DelayedJob has downsides at scale
Slide 49
Slide 49 text
• Overhead of relational database
DelayedJob has downsides at scale
Slide 50
Slide 50 text
• Overhead of relational database
• Workers monitored from outside
DelayedJob has downsides at scale
Slide 51
Slide 51 text
• Overhead of relational database
• Workers monitored from outside
• Frequently needs workers to restart
DelayedJob has downsides at scale
Slide 52
Slide 52 text
• Overhead of relational database
• Workers monitored from outside
• Frequently needs workers to restart
• Hard to keep track
DelayedJob has downsides at scale
Slide 53
Slide 53 text
Resque scales
Slide 54
Slide 54 text
• Redis
Resque scales
Slide 55
Slide 55 text
• Redis
• Parent-child forking for workers
Resque scales
Slide 56
Slide 56 text
• Redis
• Parent-child forking for workers
• Rarely needs workers to restart
Resque scales
Slide 57
Slide 57 text
• Redis
• Parent-child forking for workers
• Rarely needs workers to restart
• Easy to keep track, since workers manage their own state
Resque scales
Slide 58
Slide 58 text
• Redis
• Parent-child forking for workers
• Rarely needs workers to restart
• Easy to keep track, since workers manage their own state
• Memory hungry
Resque scales