Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

the article is didactic, focusing on overall architecture, furthermore it says it clearly on the subtitle.

     "...so you can appreciate the libraries that do it for you "


Do you know of any rpc libraries that hide the failure modes of the network from the application?


nfs.

nfs as originally designed could not fail. so what happens when something that can not fail has a failure? that's right it hangs.

On the one hand this was kind of fun, network problems, the application hangs waiting on nfs, two days later you get everything sorted out and the application comes back never knew there was a problem.

On the other hand, this is the most infuriating behavior possible, everything you touch on the system starts freezing up. and you wish it would just fail so you could fix the infernal thing.

Later the "soft" option was added so that nfs could actually fail.


The point is to show the big picture.

It's true that error management is critical for a production environment, but from a pedagogic point of view, they can left as an "exercise for the reader".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: