- Paperback: 454 pages
- Publisher: O'Reilly Media; 1 edition (May 18, 2007)
- Language: English
- ISBN-10: 9780596529260
- ISBN-13: 978-0596529260
- ASIN: 0596529260
- Product Dimensions: 7 x 0.9 x 9.2 inches
- Shipping Weight: 1.4 pounds
- Average Customer Review: 68 customer reviews
- Amazon Best Sellers Rank: #229,279 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
RESTful Web Services Paperback – May 15, 2007
Customers who bought this item also bought
Customers who viewed this item also viewed
Web services for the real world
About the Author
Leonard Richardson (http://www.crummy.com/) is the author of the Ruby Cookbook (O'Reilly) and of several open source libraries, including Beautiful Soup. A California native, he currently lives in New York.
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.
Read reviews that mention
Showing 1-8 of 68 reviews
There was a problem filtering reviews right now. Please try again later.
- Provides rigorous (and somewhat academic) description of RESTful-ness and Resource Oriented Architecture (ROA)
- Wonderful book if you have complex and large data
- This book is great for intended audiences:
-- web app/service architect/designers
-- who have complex / large data
-- who are looking to surface those data via web service and web applications
-- who think good organization is very very important (a little bit of OCD would help :)
- Not wonderful book if you do not have complex and large data
- It would be boring or irrelevant for:
-- a reader who doesn't satisfy any of the above criteria
The authors are geniuses and have deep knowledge on the whole web space. They also have firm idea on how web-apps and web-services have to be designed to make the entire web better organized, while (almost succeeding in) not being a religious fanatic on the design principles. Hence their presentation is deep and insightful. It opens up your eyes on simple, yet overarching principles of web (HTTP, URI, ...) and teaches you how considering RESTful-ness would improve your web service / app architecture.
Like some geniuses, there writing style could be sometimes lengthy and pedantic, not compact. But their writing is still crisp and precise. Academic-degree preciseness. That may be why some are put off by this book but I view it as a small price to pay to learn from their wisdom.
I found this book while designing REST API to use for our existing web application. Our web-app is a niche player, but very large and complex system and I was looking to add REST API to make the whole system more "modern". I had some doubt about the book from reading some of negative reviews, but after I completed reading it (on kindle during 8-hour flight), I was sold. The book answered my short term questions, and something much, much bigger and fundamental: RESTful way of looking at web service and applications. It actually convinced me that our web-app could have been designed much better had we known of RESTful / ROA principles and applied them early on. I definitely will remember to re-read this book when our web app/service project comes along.
If you've used SOAP and/or other Web Services-related technologies/schemas/etc. etc. etc. you should have no problem following this. For beginners, however, it is definitely not the place to start. You will need to read-up a bit more on Web Services in general and some of the options and practices out there.
The repetition in the book isn't so bad. It drives home a lot of good points and covers quite a bit of in-depth information (sometimes too much, but it has come in handy when talking with other professionals/engineers).
To work with Web Services and not have at least glanced over this book would be a huge mistake. Just be careful: it may take you a while to get through. It does get a little boring from time to time.
You may desire to stay completely RESTful in your design principals but as we know "in theory, theory and practice are the same, but in practice they are different." and sometimes you can't stick to architectural theory when implementing a solution. This book explains why its okay to make those tradeoffs and how to do them in a way that's "not so bad".
PS I made the mistake of also buying "REST in Practice". Skip that book and read this book instead.