Product Details
Restful Web Services

Restful Web Services
By Leonard Richardson, Sam Ruby

List Price: $39.99
Price: $26.39 & eligible for FREE Super Saver Shipping on orders over $25. Details

Availability: Usually ships in 24 hours
Ships from and sold by Amazon.com

58 new or used available from $13.15

Average customer review:

Product Description

"Every developer working with the Web needs to read this book." -- David Heinemeier Hansson, creator of the Rails framework

"RESTful Web Services finally provides a practical roadmap for constructing services that embrace the Web, instead of trying to route around it." -- Adam Trachtenberg, PHP author and EBay Web Services Evangelist

You've built web sites that can be used by humans. But can you also build web sites that are usable by machines? That's where the future lies, and that's what RESTful Web Services shows you how to do. The World Wide Web is the most popular distributed application in history, and Web services and mashups have turned it into a powerful distributed computing platform. But today's web service technologies have lost sight of the simplicity that made the Web successful. They don't work like the Web, and they're missing out on its advantages.

This book puts the "Web" back into web services. It shows how you can connect to the programmable web with the technologies you already use every day. The key is REST, the architectural style that drives the Web. This book:
  • Emphasizes the power of basic Web technologies -- the HTTP application protocol, the URI naming standard, and the XML markup language
  • Introduces the Resource-Oriented Architecture (ROA), a common-sense set of rules for designing RESTful web services
  • Shows how a RESTful design is simpler, more versatile, and more scalable than a design based on Remote Procedure Calls (RPC)
  • Includes real-world examples of RESTful web services, like Amazon's Simple Storage Service and the Atom Publishing Protocol
  • Discusses web service clients for popular programming languages
  • Shows how to implement RESTful services in three popular frameworks -- Ruby on Rails, Restlet (for Java), and Django (for Python)
  • Focuses on practical issues: how to design and implement RESTful web services and clients
This is the first book that applies the REST design philosophy to real web services. It sets down the best practices you need to make your design a success, and the techniques you need to turn your design into working code. You can harness the power of the Web for programmable applications: you just have to work with the Web instead of against it. This book shows you how.

Product Details

  • Amazon Sales Rank: #10953 in Books
  • Published on: 2007-05-08
  • Original language: English
  • Number of items: 1
  • Binding: Paperback
  • 446 pages

Features

Editorial Reviews

About the Author

Sam Ruby is a prominent software developer who has made significant contributions to the many of the Apache Software Foundation's open source projects, and to the standardization of web feeds via his involvement with the Atom web feed standard and the popular Feed Validator web service. He currently holds a Senior Technical Staff Member position in the Emerging Technologies Group of IBM. He resides in Raleigh, North Carolina.


David Heinemeier Hansson is a partner in 37signals and the creator of the Web-application framework Ruby on Rails. For his work on Rails, he won Best hacker of the Year 2005 at OSCON from Google and O'Reilly, in 2006, he accepted the Jolt award of product excellence for Rails 1.0

Customer Reviews

Good but pedantic and repetitious3
Ok, the concept behind the book is valid: let's have computers use the web the way it was intended to be used, and if everybody sticks to a small set of reasonable design rules, we'd all be better off. But why does it take 400 pages for the authors to drive that point home (over and over again)? 70% of the content seems "filler" material, which has been put in just to turn this into a book. True, there are code examples that may be helpful to some beginner programmers, but I'm still left feeling that this could have been a well-written, 3-chapter book about 100 pages long.

I'm still glad I read it but found the blabbing rather frustrating. My 2c.

Brilliant and Horrible4
Packed with all sorts of knowledge about REST, HTTP and AJAX this book will make you very capable at building well designed RESTful web services. Any topic imaginable is covered, from obscure ways of handling transactions, to Apache proxies, service implementations in Rails and the limitations of the current browser security model.

While this is all good and useful stuff, it also scatters the books focus, which eventually turns out to be its major problem. The topic orientation simply sucks. I would recommend reading the book in this order:

* Core knowledge
- Introduction, Chapter 1 and 3
- Chapter 4, 8, 9
- Optional: chap 10 (comparison to SOAP).

* REST service examples
- Chapter 5, 6 and 7

* REST clients
- Chapter 2 and 11

The service examples (chapter 5 - 7) should really have been one chapter. The client chapters does not show how to write clients against the provided example services, which is a major mistake. The core knowledge scattered throughout chapter 4, 8 and 9 (like the ATOM publishing protocol which is covered multiple places) should be collected and ordered.

So why the four starts ?. I have to admit that my annoyance with the books topical layout is trumped by the authors knowledge and their ability to pack a surprising number of usable facts into this book. So if you do not loose your way in their topical jungle then you will eventually come through as a REST maven.

Nearly Abysmal2
1) The editors were apparently on vacation. There are numerous errors including several typographical errors that a simple spell-check would have caught (words like "ang" and "extrenal") and a number of ungrammatical sentences.
2) The authors frequently make best practices statements without actually supporting them with evidence or otherwise explaining what makes them best practices.
3) There's really only about 100 pages of content. The other three quarters of the book is repetition. For example, chapters 4 and 8 seem to be the same. There is even a specific example regarding content language that is presented in chapter 4 and not referred to but simply repeated in chapter 8.

This book could be obsoleted by a brief 3 part tutorial perhaps combined with a half-hour slide show.