Monday, September 1, 2008

End-To-End Arguments in System Design

End-To-End Arguments in System Design

More emphasis on APIs as the primary design problem
You have to have end-to-end, as there are too many failure cases.
end-to-end meaning check and verify, generally
non end-to-end solutions (TCP) are only optimizations
When to end? Presumably when we hit hardware levels of risk
great example on delivery
don't care about acks, system could die after packet received. You want application ack
E2E Duplicate packets: what if application sends multiple packets?
Need E2E, if implicitly.
Remind me to name my distributed file system something other than SWALLOW
Not enough discussion of the performance optimizations of pushing it into the network
E2E as users making calls. That's pretty funny.

No comments: