redis-namespace: when one sidekiq process is not enough
Few months ago I was working in a project in which we had two applications communicating with each other. Each of them had to has its own sidekiq process, but they were deployed to one server. After some time, I realized that after deploying one app, the second one has problems with invoking its workers. The problem was that sidekiq was restarting and loading workers only from one (last deployed) app. So after each deploy I had many errors saying that.
redis-namespace: when one sidekiq process is not enough #ruby #rails #rubyonrails #bosnia #programming #tutorials #rubydeveloper #railsdeveloper