ActiveJob: A Service Oriented Architecture
summary
ActiveJob in Rails 4.2 provides a stable interface to queue systems like Delayed_Job/Sidekiq and powers ActionMailer async delivery, plus GlobalID for automatic record lookup. The concrete claim is that service objects (one public method, e.g. accept invite) can live in app/jobs and be run with perform_later or perform_now, letting teams swap queues and run business logic outside requests. Warning: don’t preoptimize — prefer defaults until real pain appears.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:10The headline feature for Rails 42 is the brand new Active Job framework
- 2:51EXTRA STUFF for ACTIONMAILER
- 3:56IN SUMMARY? Good Thing
- 4:31THERE'S A LOT OF CHAT ABOUT ARCHITECTURE inside RAILS APPS
- 5:57PLAIN OLD RUBY OBJECTS
- 14:15advanced ARCHITECTURE CAN BE A MISTAKE
- 15:02USE THE JOB TEST TO HELP YOUR THINKING
- 15:30YAGNI Seriously
- 16:00EMBRACE THE FRAMEWORK
related talks
41mInside ActiveJob
20mSolid Queue - Default Active Job Adaptor in Rails 8
55mThe Past, Present and Future of Background Job...
23mLook Ma, No Background Jobs: A Peek into the Async Future
34mInside Active Storage: a code review of Rails' new framework
40mAttraction Mailbox - Why I love Action Mailbox
34mSOA and the Monolithic Rails App Anti-Pattern
34mAttraction Mailbox - Why I love Action Mailbox