> Whenever the plumbing does not guarantees EOIO but the business demands it, it gets pushed into the app layer where TCP (retries and acks) is reimplemented, t

> Whenever the plumbing does not guarantees EOIO but the business demands it, it gets pushed into the app layer where TCP (retries and acks) is reimplemented, to various success levels. Interesting! You're saying the exact opposite of what Tyler Treat is saying: > Even with smart middleware, problems still leak out and you have to handle them at the edge—you’re now being taxed twice. This is essentially the end-to-end argument. Push responsibility to the edges, smart endpoints, dumb pipes, etc. It’s the idea that if you need business-level guarantees, build them into the business layer because the infrastructure doesn’t care about them. (source: http://bravenewgeek.com/smart-endpoints-dumb-pipes/ http://bravenewgeek.com/smart-endpoints-dumb-pipes/) What do you think of his argument?