Dnia środa, 16 maja 2012 21:37:24 Roberto De Ioris pisze: > > 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. > > If i understand correctly: > > the client send a request to a specific ip:port where the tcp-router is > bound. > > the tcp-router has a subscription system for mapping its ip:port tuple to > 1..N https-router > > each https-router has a bunch o uwsgi-nodes subscribed managing content > (dynamic apps or static file) > > What is really obscure to me is how to manage https sessions, the vast > majority of https load balancers i have seen, simply use the source ip to > route always to the same node.
Yes, and this is how people deploy https load balancing using haproxy, they use tcp mode and source balancing. There is patch for nginx that add support for storing SSL sessions in memcached, so with session reuse enabled client can send requests to any backend server. [1] http://hezmatt.org/~mpalmer/blog/2011/06/28/ssl-session-caching-in- nginx.html [2] http://hezmatt.org/~mpalmer/blog/2011/07/24/followup-to-ssl-session- caching-with-nginx.html [3] http://wiki.nginx.org/3rdPartyModules#Third_party_patches I see that stud also has such feature: https://github.com/bumptech/stud/pull/29 maybe it would be wise to just add it to backends, but then I still need a way to forward traffic to it :) Łukasz Mierzwa _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
