Skip to main content

Timeline for How to keep applications stateless

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Sep 26, 2023 at 8:45 comment added Ewan it's not about avoiding the data, its about handling it in a performant way,
Apr 12, 2017 at 14:53 comment added user251748 All this discussion about trying to avoid the hot potato really mystifies me. Whatever happened to the old saying, "The buck stops here"? Something has to manage the data, my bank would not like me keeping all of my financial transaction info only on my laptop. Why is everyone running away screaming from data? It is why we have computers! Crazy.
Apr 11, 2017 at 10:24 comment added Ewan no, there is an inherent problem if you hold that per session data. either you move it off the webserver to its own high availablity system or get rid of it all together by moving it to the client
Apr 10, 2017 at 21:07 comment added JeffO There's plenty you can do if pulling data from the disk is the bottleneck such as caching.
S Apr 10, 2017 at 20:20 history suggested Peter Mortensen CC BY-SA 3.0
Copy edited (e.g. ref. <https://en.wiktionary.org/wiki/bottleneck#Noun> and <http://en.wiktionary.org/wiki/won%27t>).
Apr 10, 2017 at 19:30 review Suggested edits
S Apr 10, 2017 at 20:20
Apr 10, 2017 at 8:38 comment added Ewan hmm kind of. If you have per user info on the server, even if its distributed you still have a scalability problem.
Apr 10, 2017 at 7:46 comment added Derek Elkins left SE While memory leaks and denial of service issues were a factor, I think a more significant driver nowadays is elasticity and robustness to failure of a web server which is, of course, also related to scalability. The idea is if a server gets overloaded or even crashes, I can just reroute future requests (and with a bit more care even replay failed requests) to new web servers without coordination or losing state (as the user sees it).
Apr 10, 2017 at 3:07 history answered Ewan CC BY-SA 3.0