With this [1] commit we are one step closer to get rid of nginx and use only uWSGI for HTTP(S) stack. If You need ideas for 1.4 roadmap I propose to add tcp router [2] (so that requests are forwarded as plain packets) and SSL support for workers (with SSL sessions stored in memcached/redis). So that SSL would be handled by backend servers and we can scale it up if needed, doing HTTPS on the load balancer is fast and simple solution to deploy, but You can't scale that easily. If You do that on the backend side it basically becomes free, with fastrouter it's very easy to add new node when needed.
[1] http://projects.unbit.it/uwsgi/changeset/b809f3abed28fce816428a0ed8cb9d73bba752c7 [2] or let haproxy do it since it's fast, solid and mature, but fastrouter is just to much fun since You don't need to touch any configuration, would it be hard to make fastrouter talk to haproxy and configure backends for it? I think someone already talked about this idea on this mailing list -- Łukasz Mierzwa _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
