In a distributed world, whenever is not going to work very well.
You might want to explore further with your background job queue system and ways to schedule jobs with it. Like for Sidekiq, there is Sidekiq Scheduler.
Have fun exploring the work of scheduled tasks/jobs.
Even with a monolithic application, it will be worth while to package your whole stack into docker containers. Service Oriented Architecture.
App as a single container, database as another container and redis/memcache as another container. You could package this whole stack with a single docker-compose file and your app on a docker image repository. This allows you to move and deploy your full stack with ease, on any machine you are working with.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In a distributed world, whenever is not going to work very well.
You might want to explore further with your background job queue system and ways to schedule jobs with it. Like for Sidekiq, there is Sidekiq Scheduler.
Have fun exploring the work of scheduled tasks/jobs.
Hi Daniel!.
For a monolithic Rails application, whenever seems to work fine.
I didn't know about Sidekiq-Scheduler, it looks cool. Definitely, I will give it a look.
Thank you so much for your recommendations!
PS: It would be very helpful if you could create a post talking about distributed systems and scheduled tasks/jobs.
Even with a monolithic application, it will be worth while to package your whole stack into docker containers. Service Oriented Architecture.
App as a single container, database as another container and redis/memcache as another container. You could package this whole stack with a single docker-compose file and your app on a docker image repository. This allows you to move and deploy your full stack with ease, on any machine you are working with.