1. Why the Web?

2. Web Services Problem Space

3. Web Problem Space
Not REST

4. Perception circa 1999
HTTP as “transport protocol”

5. Perception circa 2004

6. Perception circa 2004
“GET”

7. Reality
I've yet to see a Web services solution that couldn't be improved by a move to the Web
Competitive

8. Reality Not saying that the Web is for everything B2C Remote session
B2B
EAI
ERP
A/V Streaming
Not saying that the Web is for everything
etc..
Others ...

9. Where REST fits
REST is more strict than the Web.

10. Why? The Web is a more loosely coupled SOA
Interface and implementation separated
“Implementation” more than just language, OS, platform, etc..
also the function performed by the code; its “type”
Stock quote impl != weather forecast impl
A client that knows, a priori, which is which, has an implementation dependency
Deploy a system, then remove all the WSDL files – what breaks?

11. Why? WSDL not part of runtime architecture of Web services systems
If you delete *.WSDL, what breaks?
HTTP as “void *”
Application-independent Facade
Deploy a system, then remove all the WSDL files – what breaks?

12. In conclusion The Web as a goal, with REST as a guide
I used to build CORBA systems
Now I build Web systems
For similar problems
The Web as a goal, with REST as a guide