Mark Baker & Stuart Charlton's tutorial on RESTful web services

1. The Web: Distributed Objects Realized! Mark Baker, Coactus Consulting Stuart Charlton, BEA Systems

4. How We Got Here The Rise of the Object Web

9. By the mid-2000s…. what about “just” the Web?

11. Understanding Distributed Object Interoperability

14. How can a web of distributed objects span organizations?

27. Exploring the Design of REST

28. A Global, Networked, Shared Information Space

29. Users Consume & Manipulate Information via Agents

30. Information Objects Must Be Identifiable

31. An Object’s Interface is separated from Implementation

32. State is exchanged in a stateless, self-describing manner

33. Handling Evolution

34. Meaning is Determined by the Context of Relationships

35. Content & Relationships May Change Over Time...

36. ...But the Identity of Information Must Remain Stable

37. The Information Space consists of Identifiable Conceptual Mappings State (at a point in time) Object

38. Instead of Objects & State, REST calls these Resources & Representations Representation (at a point in time) Resource

39. The conceptual mapping should remain consistent over time! Concept Representation (at a point in time) Resource “ Customer 31319” Concept “ The state of Customer 31319 at a point in time” Server Client (stable)

40. Example: Different Representations Concept XML Document Resource “ Customer 31319” Concept “ The state of Customer 31319 at a point in time” Server Client (stable) CSV File

41. Multi-Organization Interoperability

42. An Organization Manages Information

43. Information Spans Organization Boundaries

44. Clients Span Organizational Boundaries

45. Clients & Infrastructure Evolve Independently

46. So, representations must be uniformly specified

48. How Stable Should the Domains of a Representation Be? Data Element Level of Stability Authority over Change Means & Intent of Communication Extremely Stable Global Representation of Information Very Stable Widely Shared Agreement Information Resource Identifier Stable Organization

49. Control Flow

50. Embed Control Flow Inside the Representation Itself

51. As Information is Manipulated or Conveyed, So Are The References for “Next Steps”

52. Hyperlinks Define the Possibilities for Communication

53. Application State is Held By the Agent

56. RESTful Web Services in Action

60. Exploring the Web Architecture Highlights

61. A View of the Current Web Architecture BEA Confidential | Web Architecture Foundation Internet Protocol Foundation Hypertext Transfer Protocol (HTTP) Security & Authentication Management & Caching BGP Application Protocol Standards ARP DNS IP TCP Multipurpose Internet Mail Extensions (MIME) Media Types HTML XML RSS / Atom URI/IRI Unicode JavaScript Images Video JSON Form data Interoperability Crawlers User Agents Semantic Web Microformats Web Sites Resource-Oriented System Interfaces Content Syndication

63. The New ORB: A Web Server

66. How Stable Should a Web Representation Be? Data Element Level of Stability Authority over Change Means & Intent of Communication (e.g. identifiers, operations & metadata) Extremely Stable Global (HTTP & URI Syntax) Representation of Information Very Stable Widely Shared Agreement (MIME Types) Information Resource Identifier Stable Organization (Allocated URIs)

70. Applied Techniques for RESTful Web Services

78. Summary

80. Thank you!

81. Alternative Architectures When is REST not appropriate?

87. References