Save Big On Open-Box & Pre-owned: Buy "RESTful Web APIs” from Amazon Warehouse Deals and save 10% off the $44.99 list price. Product is eligible for Amazon's 30-day returns policy and Prime or FREE Shipping. See all Open-Box & Pre-owned offers from Amazon Warehouse Deals.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
RESTful Web APIs 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Windows 10 For Dummies Video Training
Get up to speed with Windows 10 with this video training course from For Dummies. Learn more.
Frequently Bought Together
Customers Who Bought This Item Also Bought
Special Offers and Product Promotions
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.
An internationally known author and lecturer, Mike Amundsen travels throughout the United States and Europe consulting and speaking on a wide range of topics including distributed network architecture, Web application development, Cloud computing, and other subjects. His recent work focuses on the role hypermedia plays in creating and maintaining applications that can successfully evolve over time. He has more than a dozen books to his credit and recently contributed to the book "RESTful Web Services Cookbook" (by Subbu Allamaraju). When he is not working, Mike enjoys spending time with his family in Kentucky, USA.
Sam Ruby is a prominent software developer who is a co-chair of the W3C HTML Working Group and has made significant contributions to many of the Apache Software Foundation's open source software projects. He is a Senior Technical Staff Member in the Emerging Technologies Group of IBM.
Top Customer Reviews
As expected from an "ideas" book, the text is peppered with first person thoughts, rhetorical questions, and very strongly held opinions (e.g., "REST beat SOAP" and "JSON beat XML".) If you buy into these, the book will feel natural and even inspired. If you don't, your hackles may get a workout.
Nevertheless, it ultimately does what any good "ideas" book should do - stimulates your thinking.
From a conceptual perspective, this book provides stellar explanations on topics that are must-knows for REST-practitioners. E.g., on the differences between protocol semantics and application semantics; and the relevance of HATEOAS when it comes to the semantic web.
A minor disappointment for me was that the "API" in the title was defined at a higher-level than I'd have liked. At its core, it merely proposes that a new API should not be a custom one-off, but instead should use standards whenever possible. As a result, it focuses on explanations of standards such as those that deal with collections, URI Templates, and hypermedia controls. However, it punts on the more prosaic elements of good REST API design - such as the identification of resources and operations, for a given domain.
This book's contents could also have benefited from better organization. Concepts were spread out geographically, and often needed a lot of paging back and forth to assemble a complete picture.
Despite these minor quibbles, I thoroughly enjoyed the read.Read more ›
It's very clearly written and accessible, and doesn't require too much knowledge to dive into. For reference, I started learning programming around 3 years ago through my current college major.
Here's the Cliffs Notes version:
The problem that the author approaches is that APIs these days are not consistent with one another or even with themselves. This causes several issues:
1) APIs are inflexible. Once you release them, it's very difficult to change them. This is ironic, since HTTP and the web is powerful because of its flexibility.
2) APIs are not machine-readable. You have to read prose documentation to figure out how they work, and every API is different. At the same time, API documentation is often not up to date or non-existent, and it's unscalable to expect all API developers to maintiain complete documentation for all the APIs that they ever work.
3) People create novel, non-standardized APIs for the same general tasks over and over again. There's a staggering amount of repeated work.
The hope is that following standards and imposing structure and metadata in your APIs will one day allow API clients to bridge what the author calls "the semantic gap," which amounts to making an API self-document itself by using standardized idioms and good RESTful web practices, a pattern that the author calls "hypermedia.Read more ›
Most Recent Customer Reviews
Not well organized. Topics are not broad enough for the feel of a full treatment of the subject. Examples are both not thorough and unclear. Read morePublished 2 months ago by Amazon Customer
I had some expectation to get from the book when I bought the book, e.g., what are the principles, best practises, trends, etc, on designing restful web APIs. Read morePublished 8 months ago by Amazon Customer
I was very impressed by his book. It provides thorough coverage of RESTful web services from q design perspective, but it's written with developers in mind, and there is plenty of... Read morePublished 13 months ago by Gregory Woodhouse
I normally don't post negative reviews, but I found this book to be very verbose. Trim half the banter and I'd give this 4 stars.Published 15 months ago by Willie W.
Most of the companies are going towards REST APIs and migrating away from SOAP. REST is platform agnostic and really cool way of writing APIs. Read morePublished 16 months ago by rpv
This book may put you to sleep. After starting to read it I found some useful websites that help learning the content better. The websites are not as thorough. Read morePublished 22 months ago by Allen
As we re-architect existing services to expose RESTful API's, we've found this book provides good reference material. Read morePublished on June 13, 2014 by J Burnett