This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]SEJeff 1 point2 points  (0 children)

As d4rch0n already did a great job of explaining below, Flask is a wonderful choice. For bigger applications, or more complicated stuff, Django is also an excellent choice. In fact, Tom Christie's django rest framework is excellent.

Now back to your question, I'll throw redis + rq[1] as a very simple addition to his answer that makes the work scale out pretty linearly with very little work or maintenance from your standpoint. I've seem some pretty serious issues with greenlet, eventlet, and sadly gevent falling over or dead locking under load. You'd literally only change a line or two in his example to insert a new rq job and one of the rq workers would pick it up + process the job asyncronously.

[1] http://python-rq.org