News for hackers. Stuff that matters.
Re:Setting Up HTTP(S) Load Balancing – WebSocket proxy support by jdub on Tuesday April 25, 2017 @09:54AM (#14193510)
There are plenty of good reasons to avoid app server state (and thus session affinity), among them: Inefficiently imbalanced load balancing can affect performance and reliability, app server changes (service restart, reboot, scale down) will drop state causing interruptions (often user visible), etc.

If you don't want unused memory on your app servers, don't provision it. :-)

Re:Setting Up HTTP(S) Load Balancing – WebSocket proxy support by caleblloyd on Tuesday April 25, 2017 @12:44PM (#14195338)
There's pros and cons to each method, as we've both pointed out. My main point is that it's not an anti-pattern, it's an architecture decision, and the pros and cons of each should be weighed when designing an app.

I just finished working on a real-time collaborative document editing service and chose to use document affinity so that the app server could handle collaboration directly. It is extremely performant and I'd choose this approach again any day versus farming out to Redis/RethinkDB/etc. It persists to a database as writes come in, and performs initial load from the database. Local memory accesses are orders of magnitude faster than going over the network, and it reaps the benefits.