I&#39;m interested in articles which have some concrete information about stateless and stateful design in programming. I&#39;m interested because I want to learn more about it, but I really can&#39;t find any good articles about it. I&#39;ve read dozens of articles on the web which vaguely discuss the subject, or they&#39;re talking about web servers and sessions - which are also &#39;bout stateful vs stateless, but I&#39;m interested in stateless vs stateful design of attributes in coding. Example: I&#39;ve heard that BL-classes are stateless by design, entity classes (or at least that&#39;s what I call them - like Person(id, name, ..)) are stateful, etc.

I think it&#39;s important to know because I believe if I can understand it, I can write better code (e.g. granularity in mind).

Anyways, really short, here&#39;s what I know &#39;bout stateful vs stateless:

Stateful (like WinForms): Stores the data for further use, but limits the scalability of an application, because it&#39;s limited by CPU or memory limits

Stateless (Like ASP.NET - although ASP tries to be stateful with ViewStates):
After actions are completed, the data gets transferred, and the instance gets handed back to the thread pool (Amorphous).


As you can see, it&#39;s pretty vague and limited information (and quite focussed on server interaction), so I&#39;d be really grateful if you could provide me with some more tasty bits of information :)

All Stateful Solutions on Gang of Coders

Total of 1 Stateful Solutions

Stateless vs Stateful