Comment Re:Didn't understand what you were reading... (Score 1) 590
You missed both the point of the article and the point of the reply.
E.g. "If you intelligently apply the rule"- what rule? What are you talking about "net"? Since when is net a persistent store? Problem original article is talking about is maintaining integrity when state is spread across multiple stores. Unfortunately a) the article does not just come out and say that and instead goes into some weird rules about inputs and outputs and b) there are (and pretty common) very legit cases where violation of this rule is required. And in those cases you should deal with any edge conditions explicitly. And no "database and log file and images and whatever else crap is the single store because it's on disk" shows that you did not understand the point of the article. "single store" is wherever you have a clear contract between yourself and the final state of the store (aka transactionality or even ACID if you are lucky). BTW, most "persistent stores" other than databases make no guarantees so even if you are using only one output you still need to enforce your own failure checks.
Rest of your response shows as much understanding. Note, that tepples is *arguing against* blunt points made in the article, not making his own. Take that in context as well.
Cheers,
---