2 ms·
We worked on the same problem, and what you described works, however it also happen to be exactly what delayed job does. Which bring me to the next point: Side
by Fire-Dragon-DoL 5y ago
We worked on the same problem, and what you described works, however it also happen to be exactly what delayed job does.
Which bring me to the next point:
Sidekiq should never be the default choice. It brings distributed systems complexity to an audience that's trained to work on a monolithic database.
Delayed job or similar should be the default, with sidekiq relegated tp jobs ready to be lost
- blueplanet200 5y agoI agree with you that people often overlook the complexity of tying changes to their database, with enqueuing jobs in a completely separate system. https://www.betterment.com/engineering/delayed-resilient-background-jobs-on-rails https://www.betterment.com/engineering/delayed-resilient-bac... does a great job explaining this.