Geek Answers Handbook

Securing Deferred Work

We are currently working on docking our Ruby on Rails application, which also includes a Delayed Job. The question that is buzzing in our development team is whether and / or how to tag the “Delayed Jobs” component separately from the application.

This will allow the Delayed Job to launch new containers when necessary to ensure high traffic in the job queue. In addition, since the Delayed Job actually launches the Rails application every time it boots for the first time, we thought the following benefits would be:

  • Delayed Job Content May Launch Faster
  • Application code is launched regardless of the launch time of the Delayed Job container
+7
ruby ruby-on-rails docker delayed-job
source share
1 answer

So, I know the guy responsible for the rails application, which uses deferred tasks. When it came time to pre-re-provision the specified application, he received a container for each. Both containers use the same code base, but one runs the interface and one task. It does not share microservice-eriffic, but it works.

Beyond the logical separation between two docker containers, there should be only one process running inside. Perhaps he hacked it together, but it was wrong to break the fundamental docker out of the gate.

+1
source share

More articles:


All Articles