REMOTE PROCEDURE CALLS Steve Vinoski Basho Technologies, Cambridge, - PowerPoint PPT Presentation

Distributed Systems BSD socket API Argus, a language/system for reliable distributed apps Xerox Cedar: the seminal Birrell/Nelson paper "Implementing Remote Procedure Calls" Eden, an OO distributed OS based on RPC Monday, October 1, 12

Distributed Systems Monday, October 1, 12

Distributed Systems Emerald, a distributed object language providing object mobility and local/remote transparency Monday, October 1, 12

Distributed Systems Emerald, a distributed object language providing object mobility and local/remote transparency ANSAware, a full-feature RPC-based system for portable distributed apps Monday, October 1, 12

RPC Everywhere Monday, October 1, 12

RPC Everywhere Monday, October 1, 12

RPC Everywhere Distributed systems research focus: full-stack systems Monday, October 1, 12

RPC Everywhere Distributed systems research focus: full-stack systems OS, language, compiler, distribution mechanisms Monday, October 1, 12

RPC Everywhere Distributed systems research focus: full-stack systems OS, language, compiler, distribution mechanisms Most used RPC as a key abstraction Monday, October 1, 12

Focus on Uniformity Monday, October 1, 12

Focus on Uniformity Local/remote transparency, location transparency Monday, October 1, 12

Focus on Uniformity Local/remote transparency, location transparency Single type system across the distributed system Monday, October 1, 12

Focus on Uniformity Local/remote transparency, location transparency Single type system across the distributed system Types checked at compile-time Monday, October 1, 12

Protocols Research systems papers rarely discussed network protocols Closed, proprietary, specialized per system Protocol was just part of "RPC black box" Monday, October 1, 12

Industrial Distributed Systems Monday, October 1, 12

Industrial Distributed Systems Vendors supplied full stacks: hardware, software, network Limited network interoperability between stacks Homogeneous systems Monday, October 1, 12

Research Into Practice Monday, October 1, 12

Research Into Practice Vendors needed to adopt distributed systems research Monday, October 1, 12

Research Into Practice Vendors needed to adopt distributed systems research But didn't want to adopt full research stacks Monday, October 1, 12

Research Into Practice Vendors needed to adopt distributed systems research But didn't want to adopt full research stacks Porting was difficult Monday, October 1, 12

Research Into Practice Vendors needed to adopt distributed systems research But didn't want to adopt full research stacks Porting was difficult Everything had to be compiled to get reasonable performance Monday, October 1, 12

Research Into Practice Vendors needed to adopt distributed systems research But didn't want to adopt full research stacks Porting was difficult Everything had to be compiled to get reasonable performance Little interest in interpreters and virtual machines Monday, October 1, 12

Standards Rapid hardware advances produced a need for software portability and interoperability Users began to have heterogeneous networks, so they wanted portable OS interfaces standard/portable programming languages standard networks and protocols Monday, October 1, 12

Languages Researchers had their own distributed languages Industry wanted standard languages Monday, October 1, 12

Research Into Practice Vendors adopted research ideas But kept their own stacks and used standard languages Monday, October 1, 12

Industrial RPC Systems Apollo's Network Computing System (NCS), an RPC system with an IDL Sun's Open Network Computing (ONC) RPC DEC, IBM, HP also had RPC-based projects Monday, October 1, 12

Internet Influence ARPANET converted to TCP/IP in 1983 Internet services such as email and file transfer continued to improve and gain popularity through the 1980s Industry started adopting TCP/IP in the latter half of the 80s Monday, October 1, 12

RPC History: The 1990s Monday, October 1, 12

Distributed Objects Monday, October 1, 12

Distributed Objects Distributed systems were popping up everywhere OOP was viewed as the way to develop software Vendors all had their own distributed objects projects Monday, October 1, 12

CORBA Industry standard comprising contributions from a variety of vendors Based squarely on 1980s research, focused on distributed objects languages (first C, then C++, others later) local/remote transparency Monday, October 1, 12

Published in 1999 Still earns royalties! :) Monday, October 1, 12

CORBA Industry standard comprising contributions from a variety of vendors Based squarely on 1980s research, focused on distributed objects languages (first C, then C++, others later) local/remote transparency Monday, October 1, 12

A Note on Distributed Computing Monday, October 1, 12

A Note on Distributed Computing Monday, October 1, 12

A Note on Distributed Computing Important 1994 paper by Jim Waldo, Ann Wollrath, Geoff Wyant, Sam Kendall Monday, October 1, 12

A Note on Distributed Computing Important 1994 paper by Jim Waldo, Ann Wollrath, Geoff Wyant, Sam Kendall Explained (again) why distributed objects and local objects were different Monday, October 1, 12

A Note on Distributed Computing Important 1994 paper by Jim Waldo, Ann Wollrath, Geoff Wyant, Sam Kendall Explained (again) why distributed objects and local objects were different latency Monday, October 1, 12

A Note on Distributed Computing Important 1994 paper by Jim Waldo, Ann Wollrath, Geoff Wyant, Sam Kendall Explained (again) why distributed objects and local objects were different latency access models Monday, October 1, 12

A Note on Distributed Computing Important 1994 paper by Jim Waldo, Ann Wollrath, Geoff Wyant, Sam Kendall Explained (again) why distributed objects and local objects were different latency access models partial failure Monday, October 1, 12

A Note on Distributed Computing Important 1994 paper by Jim Waldo, Ann Wollrath, Geoff Wyant, Sam Kendall Explained (again) why distributed objects and local objects were different latency access models partial failure concurrency Monday, October 1, 12

" Communications protocol development has tended to follow two paths. One path has emphasized integration with the current language model . The other path has emphasized solving the problems inherent in distributed computing . Both are necessary, and successful advances in distributed computing synthesize elements from both camps. " —A Note on Distributed Computing Monday, October 1, 12

Fallacies of Distributed Computing The network is reliable There is one administrator Latency is zero Transport cost is zero Bandwidth is infinite The network is The network is secure homogeneous Topology doesn't change FROM HTTP://EN.WIKIPEDIA.ORG/WIKI/FALLACIES_OF_DISTRIBUTED_COMPUTING Monday, October 1, 12

Distributed Java Monday, October 1, 12

Distributed Java Various Java distributed computing projects, too many to cover here But large parts of Java adopted CORBA Later, CORBA adopted ill-conceived "Objects By Value" and "Reverse Java-IDL Mapping" specs to allow Java objects to be passed over the wire Monday, October 1, 12

The Rise of the Web Monday, October 1, 12

The Rise of the Web CORBA and Java focused on the enterprise and later, SOAP Meanwhile, the Web was taking over the world Monday, October 1, 12

Distributed Objects! Monday, October 1, 12

Distributed Objects! The Web is arguably distributed objects too, but: Monday, October 1, 12

Distributed Objects! The Web is arguably distributed objects too, but: fixed set of methods Monday, October 1, 12

Distributed Objects! The Web is arguably distributed objects too, but: fixed set of methods hypermedia coupling Monday, October 1, 12

Distributed Objects! The Web is arguably distributed objects too, but: fixed set of methods hypermedia coupling language independent Monday, October 1, 12

Distributed Objects! The Web is arguably distributed objects too, but: fixed set of methods hypermedia coupling language independent designed specifically for large-scale networks Monday, October 1, 12