3 ms·

> If you need some bizarre stateless property for horizontal scaling your sessions... > It is overwhelmingly likely that you do not needed crazy horizontal sca

> If you need some bizarre stateless property for horizontal scaling your sessions... > It is overwhelmingly likely that you do not needed crazy horizontal scaling schemes at all, and that a single server-side session management system is sufficient for your use case... This feels quite short-sighted to me, even in 2017. Architecture for supporting highly available systems and so-called "crazy" horizontal scaling are not so different from each other, and pretty much everyone can benefit significantly from a highly available and fault tolerant architecture. Stateless application architecture is significantly helpful in keeping a system simple and easy to deploy, which has huge impacts on overall development processes, ability to remediate vulnerabilities and ability to respond to changing requirements.

andybak 7y ago
> pretty much everyone can benefit significantly from a highly available and fault tolerant architecture. Yes but these are very hard problems and you've only given one side of the cost benefit equation.
- bshacklett 7y ago
  What are the problems that haven't been solved? Stateless application servers have been reasonably commonplace for years, now, which is the main hurdle that I've needed to surmount. The majority of other issues can be handled at the platform level. It's a lot of work to refactor an application, and sometimes that doesn't make sense, but a blanket dismissal of the usefulness of proper architecture because an application isn't running at Google or Facebook's scale does little to help push technology and practices forward.