Surely your Rails app flies, no request takes longer than 60 seconds to complete, ever. You’ve proven that Rails can scale and all that jazz. Surely you’ve really spent the time to read the nginx wiki and customize Ezra’s nginx.conf to such a degree that you can handle thousands of concurrent requests at any given time. You know, Rails scales…
Now some of us develop fairly intricate systems using Rails. Systems that have long running reports, or systems that connect to other systems to execute commands, or obtain information. Whatever the reason, somethings just can’t complete within 60 seconds, and if your users understands the complexity of the background tasks they’ll quite happily press a button and go make coffee while the server crunches away at the reports.
I head one such project, and had the most interesting issue I just solved. And it involved reading a lot on nginx’s fine print…
