<<< Previous speaker next speaker >>>

Jim Webber, Author of "Developing Enterprise Web Services - An Architect's Guide"

 Jim  Webber

Dr. Jim Webber is the Global Head of Architecture for ThoughtWorks where he works with clients on delivering dependable service-oriented systems. Jim was formerly a senior researcher with the UK E-Science programme where he developed strategies for aligning Grid computing with Web Services practices and architectural patterns for dependable Service-Oriented computing. Jim has extensive Web Services architecture and development experience as an architect with Arjuna Technologies and was the lead developer with Hewlett-Packard on the industry's first Web Services Transaction solution.

Jim is an active speaker in the Web Services space and is co-author of the book "Developing Enterprise Web Services - An Architect's Guide" in addition to being a contributing author to other books and articles.

p>Jim holds a B.Sc. in Computing Science and Ph.D. in Parallel Computing both from the University of Newcastle upon Tyne. His blog is located at http://jim.webber.name.

Training: "REST in Practice - A Tutorial on Web-based Distributed Systems"

Track: Tutorial

Time: Monday 09:00 - 16:00

Location: Abbey Room

Abstract:

The Web is fast becoming a serious competitor to traditional enterprise architecture approaches. This tutorial will provide an introduction to RESTful Web Service techniques, both from a theoretical and practical perspectives. The tutorial is broken down as follows:

  • Introduction and Motivation
  • The Web Architecture
  • Simple Web Integration including POX and URI tunnelling
  • CRUD Services using URI templates and HTTP
  • Semantics using Microformats and RDF
  • Hypermedia and the REST architectural style
  • Scalability and how a text-based client-server polling protocol outperforms everything else!
  • ATOM and ATOMPub for event-driven and pub/sub applications Security
  • Conclusions and further thoughts

Participants should be comfortable with distributed computing concepts, but won't need any particular integration or middleware experience.