I was working on project where I had to update user account on third party server. This process was taking long time(i.e. 3-5 secs). Hence we decided to pass this service on Sidekiq worker and proceed ahead in request flow. Meantime frontend had loader that informed user to wait for some time. As soon as we got response from third party server, we have to inform frontend. I tried server solutions and then I came to use of Redis and Synchronous Sidekiq Worker to rescue me.
Sidekiq Workers and frontend are not related. Workers are asynchronous. They are running somewhere and frontend does not know where. So, basically we need to store the response somewhere and pull out that response back to frontend. I used Redis to store sidekiq worker response and pulling out that for frontend. There may be other work around.
Redis and Synchronous Sidekiq Worker:
This button does ajax call to create method of counter controller. The job for create method is to call HardWorker several time synchronously. The real problem is, we want to inform frontend about the response of our hard working guy.
Here I have hard worker which does really hard work!! It does some task, in our case it sleeps for a second. After that it store counter value to Redis store and that we need to pull out.
I use ajax call to my counter controller show method with a second span. Here the job for show method is pulling out data from Redis and inform frontend about it.
The data coming from show method response is populating over the page by jQuery. This is very generic solution. There are several methods for storing and pulling out data.You can store values to some file or mongo db and read it back. You can this code modify as per your requirements and plug in to your application.
This solution has one limitation.
- frontend has to know the `key` name that is used to store sidekiq response in Redis
You can find code here on GitHub