> The main thing one needs to think about when coding an app in a load balanced environment is that there’s no guarantee that request ‘n+1′ is going to land on the same server as request ‘n’, so you need to handle sessions in a centralized/db manner so that the cookies in the browser link you up to the proper session regardless of what server you hit.
Instead of doing it in a centralized/db manner, Beaker allows sessions to be distributed client side:
Comments
> The main thing one needs to think about when coding an app in a load balanced environment is that there’s no guarantee that request ‘n+1′ is going to land on the same server as request ‘n’, so you need to handle sessions in a centralized/db manner so that the cookies in the browser link you up to the proper session regardless of what server you hit.
Instead of doing it in a centralized/db manner, Beaker allows sessions to be distributed client side:
http://techspot.zzzeek.org/2011/10/01/thoughts-on-beaker/
It was one of the best things I learned last year.
Could we have a tl;dr version please?