4 ms·

re 1 - better design a program with no state beyond configurations.

• gabbo 11y ago
  Easier said than done, if you don't have any state you're probably not doing something all that interesting. The trick is to keep your state in the right place, the answer usually being to punt state management to a database/message queue/etc. - you definitely want to avoid, say, stateful frontends.