Evan Martin (evan) wrote in evan_tech,
Evan Martin

rpc note

graydon linked me to this note about distributed computing. And he oughta know, 'cause he spent a lot of time on Berlin (aka Fresco, which was actually referenced in this paper).

The whole thing feels relevant to a lot of stuff I've written about here, even beyond the obvious RPC comparisons. I kept thinking of all of the arguments about the wire format for these blogging protocols, and especially that article that criticized the simple-text LJ protocol for "escaping issues". There's been talk on the Atom lists for sending deltas efficiently, as if figuring out what to rename all the RSS nodes to* was the hard problem and tacking on distribution will be easy.
The hard problems in distributed computing are not the problems of how to get things on and off the wire. The hard problems in distributed computing concern dealing with partial failure and the lack of a central resource manager. The hard problems in distributed computing concern insuring adequate performance and dealing with problems of concurrency. The hard problems have to do with differences in memory access paradigms between local and distributed entites. People attempting to write distributed applications quickly discover that they are spending all of their efforts in these areas and not on the communications protocol programming interface.

* I'm kidding (on the square).

  • memcache job offers

    I get occasional recruiter spam that specifically calls out "my work on memcached". This is pretty funny because all I did was make some trivial…

  • application stack

    "Put yourself in 1995. I'm going to tell the you of 1995 that in 2010, there will be a software platform with the following properties:" Luis Villa…

  • münchen

    On that note: I'm living in Munich for the next week plus a few days. Do I know anyone around here? (PS: The LJ → PubSubHubbub → Reader…

  • Post a new comment


    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.