title: Stateless vs Stateful
body: <p>I'm interested in articles which have some concrete information about stateless and stateful design in programming. I'm interested because I want to learn more about it, but I really can't find any good articles about it. I've read dozens of articles on the web which vaguely discuss the subject, or they're talking about web servers and sessions - which are also 'bout stateful vs stateless, but I'm interested in stateless vs stateful design of attributes in coding. Example: I've heard that BL-classes are stateless by design, entity classes (or at least that's what I call them - like Person(id, name, ..)) are stateful, etc.</p>
  <p>I think it's important to know because I believe if I can understand it, I can write better code (e.g. granularity in mind).</p>
  <p>Anyways, really short, here's what I know 'bout stateful vs stateless:</p>
  <p>Stateful (like WinForms): Stores the data for further use, but limits the scalability of an application, because it's limited by CPU or memory limits</p>
  <p>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).</p>
  <p>As you can see, it's pretty vague and limited information (and quite focussed on server interaction), so I'd be really grateful if you could provide me with some more tasty bits of information :)</p>