Sounds good. 

But in my case, the response would not take too long and sometimes it's just a matter of sec.

I am not very confident about the feasibility of breaking a single request into 3 requests from the user point of view but will discuss with my colleagues about this solution.

Thanks @Danny Wijnschenk 

While using JOB command, I think it was timeout on the Postman and it was still running in the server filling up my logs rapidly until I restarted the Cache server but that could be because of the code issue.

But the problem for me was, even though user sends multiple requests simultaneously the API endpoint will process them one by one and the first request needs to be responded before processing the second. Since, JOB runs in the background, I was not able to reply the response data for each request. 

Similarly, while implementing Work Queue Manager, I don't have the list of requests and cannot collect them in one place and process one by one with response back to each request.

 Or I may be complicating things here and identifying the request from the same user and waiting until the previous request completes would just be a perfect solution for me?

Hi @Timo Lindenschmid and @Pietro Montorfano ,

Thank you for you suggestions, these are really good stuffs you have shared but I had to stick with $ZF(-1) at the moment as it is working as expected with the current Cache version we are using.

I am sure your thoughts will help other developers with similar issue.