What's the most scalable way to handle somewhat large file uploads in a Python webapp?

Posted by Jason Baker on Stack Overflow See other posts from Stack Overflow or by Jason Baker
Published on 2010-05-20T17:17:10Z Indexed on 2010/05/20 17:20 UTC
Read the original article Hit count: 198

Filed under:
|
|
|

We have a web application that takes file uploads for some parts. The file uploads aren't terribly big (mostly word documents and such), but they're much larger than your typical web request and they tend to tie up our threaded servers (zope 2 servers running behind an Apache proxy).

I'm mostly in the brainstorming phase right now and trying to figure out a general technique to use. Some ideas I have are:

  • Using a python asynchronous server like tornado or diesel or gunicorn.
  • Writing something in twisted to handle it.
  • Just using nginx to handle the actual file uploads.

It's surprisingly difficult to find information on which approach I should be taking. I'm sure there are plenty of details that would be needed to make an actual decision, but I'm more worried about figuring out how to make this decision than anything else. Can anyone give me some advice about how to proceed with this?

© Stack Overflow or respective owner

Related posts about python

Related posts about fileupload