InfoQ Homepage Presentations RPC and its Offspring: Convenient, Yet Fundamentally Flawed
RPC and its Offspring: Convenient, Yet Fundamentally Flawed
Summary
In this presentation from QCon London 2009, Steve Vinoski discusses what RPC means, the origin and history of RPC, RFC 707, the origins of Distributed Computing Environment (DCE), the growth of the Internet, standardization, distributed objects, CORBA, DCOM, Java, SOAP, WS-*, the fundamental flaws in RPC, REST properties and constraints, REST vs RPC philosophy, Erlang reliability and concurrency.
Bio
Steve Vinoski is a member of technical staff at Verivue, a startup in Westford, MA, USA. He was previously chief architect and Fellow at IONA Technologies (now part of Progress Software) for a decade, and prior to that held various software and hardware engineering positions at Hewlett-Packard, Apollo Computer, and Texas Instruments.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Community comments
Not valuable presentation from a guy that recommended CORBA
by Pedro Gonzalez,
Re: Not valuable presentation from a guy that recommended CORBA
by Luis Espinal,
Not valuable presentation from a guy that recommended CORBA
by Pedro Gonzalez,
Your message is awaiting moderation. Thank you for participating in the discussion.
This is not a valuable presentation.
Steve Vinoski explains the history of RPC in his own eyes.
You should not care much about someone that recommended CORBA.
Re: Not valuable presentation from a guy that recommended CORBA
by Luis Espinal,
Your message is awaiting moderation. Thank you for participating in the discussion.
Ad hominem. The guy indeed admits that it was a bad idea and explains why. Shouldn't that have technical merit? Or should go juvenile and firmly say "hahaha, you made a mistake, from now one and for all of eternity you will never be able to say anything of value because I say so"?