Hi all, I would like give more details on this by giving our current issue and the way how we do thing:

Our current implementation:

1. We have a web application (and MVC with HTML/JQuery front-end and ASP.NET web service asmx back end)
2. Our application have a feature when user can print multiple-orders, which can results in hundreds of page PDF file.
3. The PDF file was generated via calling directly from our Web Service to SQL Server Reporting Services (SSRS) or a worker service (that can produce PDF file) for printing.
4. The result then returned to client via HTTP Response.
5. User can then save that file /or open in new browser tab for printing.

The issue: When user choose to print multiple orders, the process either take too long, then get time out (to SSRS) or that process can slow down our web server significantly.

My question is: What is the correct/best way to handle printing multiple PDF files and/or execute long running tasks nowadays in a ASP.NET Web application?

​

• Given that we try to avoid to use solution like back-end worker processing then user can download the file later
• Is ASP.NET still be able to support this kind of demand (long running task)? Or what .NET technology which I should choose?
• What is "modern" solution nowadays in .NET web application architecture?