用于将上传传递给第三方的ASP.Net架构(ASP.Net architecture for passing upload to third party)

 我正在开发一个专门用于站在YouTube API之上的应用程序，并将用户上传的内容传递到YouTube.Videos.Insert端点（使用他们提供的.NET客户端库）。 现在，我的应用程序是作为一个简单的ASP.NET MVC应用程序构建的，但我很快意识到这可能不是最好的方法，因为问题很快就会发现上传过程可能是一个相当长时间运行的过程。 
 
 为了有效地做到这一点，最佳实践架构会是什么？ 到目前为止我的想法是： 
 
 
 
 某种排队策略，MVC应用程序将上传内容放入队列，后台进程将其弹出并执行进一步上传到YouTube。 但这似乎效率低下，因为它会临时存储文件并再次检索它以处理应用程序的总体开销。 
 
 
 一个单独的微服务API，带有一个端点，用于接收实际上传，我将通过我的应用程序前端的Javascript联系; 它将接收该文件，返回202 Accepted，并将上传流传递到异步线程并立即处理。 这似乎更有效但我担心可扩展性，如果除了我以外的任何人最终使用这个东西。 
 
 
 我希望有更多的架构洞察力来解决这个问题的最佳方法。 

I'm working on an application which is designed to stand on top of the YouTube API and pass uploads from the user to the YouTube.Videos.Insert endpoint (using the .NET client library they provide). Right now, my application is built as a simple ASP.NET MVC application, but I'm quickly realizing that may not be the best approach, because the issue quickly crops up that the upload process could be a rather long-running one. 
 
What would the best-practice architecture be in order to do this effectively? My ideas thus far are:
 
 
 
Some sort of queue strategy, where the MVC app puts the upload on the queue, and a background process pops it off and performs the further upload to YouTube. This seems inefficient, though, since it adds storing the file temporarily and retrieving it again for processing to the overall overhead of the application.
 
 
A separate microservice API with an endpoint for receiving the actual upload, which I would contact via Javascript from the front-end of my app; it would receive the file, return a 202 Accepted, and pass the upload stream off into an async thread and process it immediately. This seems more efficient but I'm worried about scalability if anyone besides me ends up using this thing.
 
 
I would love additional architecture insight on the best way to approach this.

原文：https://stackoverflow.com/questions/46286257