CDN$ 38.43
  • List Price: CDN$ 58.34
  • You Save: CDN$ 19.91 (34%)
Only 3 left in stock (more on the way).
Ships from and sold by Amazon.ca. Gift-wrap available.
Quantity:1
RESTful Web APIs has been added to your Cart
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

RESTful Web APIs Paperback – Sep 30 2013

3.5 out of 5 stars 2 customer reviews

See all 3 formats and editions Hide other formats and editions
Amazon Price
New from Used from
Kindle Edition
"Please retry"
Paperback
"Please retry"
CDN$ 38.43
CDN$ 35.07 CDN$ 53.33

Harry Potter and the Cursed Child
click to open popover


Frequently Bought Together

  • RESTful Web APIs
  • +
  • RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity
  • +
  • Building Microservices
Total price: CDN$ 116.20
Buy the selected items together

No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
Getting the download link through email is temporarily not available. Please check back later.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.




Product Details

  • Paperback: 406 pages
  • Publisher: O'Reilly Media; 1 edition (Sept. 30 2013)
  • Language: English
  • ISBN-10: 1449358063
  • ISBN-13: 978-1449358068
  • Product Dimensions: 17.9 x 2.1 x 23.3 cm
  • Shipping Weight: 812 g
  • Average Customer Review: 3.5 out of 5 stars 2 customer reviews
  • Amazon Bestsellers Rank: #94,841 in Books (See Top 100 in Books)
  •  Would you like to update product info, give feedback on images, or tell us about a lower price?

  • See Complete Table of Contents

Product Description

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.


What Other Items Do Customers Buy After Viewing This Item?

Customer Reviews

3.5 out of 5 stars
5 star
0
4 star
1
3 star
1
2 star
0
1 star
0
See both customer reviews
Share your thoughts with other customers

Top Customer Reviews

Format: Paperback
The idea of a RESTful web API is a confusing thing for a lot of people. If you have any doubts about what you are doing with Web API's, this book will clear that up for you.

I won't lie, this book is very dry. The subject matter is great for reference, but very difficult to just sit down and read. Throughout RESTful web APIs, the author's are jumping from project to project, illustrating the actual point of having a RESTful API in the first place. From the "don't just use GET", to "DELETE can actually be used for something", they don't pull any punches about what you've been doing wrong with your project to actually make a RESTful API.

I do have to say, I'm going to hold on to this book for reference whenever I am writing a design document. Figuring out your routing is much easier when you have the reference backing of these obviously more brilliant than me developers telling you when you are doing something right.

For entertainment value, I'd give this book a 2 on a scale of 1 to 10. As far as useful, meaningful material? 10 out of 10, easily. Pick it up for your next API project, and finally set yourself straight.
One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback Verified Purchase
Not a bad book, but a little preachy.
One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse

Most Helpful Customer Reviews on Amazon.com (beta)

Amazon.com: HASH(0x9ae2ce28) out of 5 stars 19 reviews
62 of 65 people found the following review helpful
HASH(0x9b23f648) out of 5 stars An "ideas" book Sept. 25 2013
By Ammy_Evaluator - Published on Amazon.com
Format: Paperback
This is an "ideas" book ... it is both implementation- and platform-agnostic, and there isn't a single line of code anywhere between its covers (except for HTML and JSON data structures.)

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.

While this book could be read by a developer at any level, it would be most appreciated by a technical lead or architect who is already familiar with basic REST concepts. Beginners to this technology might be better served by Bill Burke's RESTful Java with Jax-RS - which also covers low level API design adequately. (Note that there is an updated edition due shortly.)

!A_E!
35 of 36 people found the following review helpful
HASH(0x9b23f69c) out of 5 stars The best I could find.... Jan. 6 2014
By Tim - Published on Amazon.com
Format: Kindle Edition Verified Purchase
... But still not great, unfortunately. The author puts a lot of effort into discouraging people from creating their own media types, link relations, etc. then spends half of the time telling us why we should use two "standard" formats that the author himself has created (Collection+JSON and ALPS). Constantly switching between JSON and XML, various scheme/profile formats are also confusing. Finally, the book is a bit condescending and too futuristic for its own good: Facebook, Flickr, Twitter, etc. have got it all wrong, and the author is going to tell us how to do things "right". Except that no examples, beyond a trivial maze game, are given of how to do things he way the author believes is correct.
11 of 11 people found the following review helpful
HASH(0x9b23f7f8) out of 5 stars REST Concepts Oct. 16 2013
By IADev - Published on Amazon.com
Format: Paperback
Only having a basic understanding of REST, this book introduced many new concepts and topics to me. For example, I had never heard of the ColIection+JSON standard or JSON-LD. Hypermedia was also a topic that I had barely heard about but was introduced to in this book. I thought it was interesting how the author called out a short process for how to add hypermedia to an existing API as well as if it was worth the effort. These are important questions to ask rather than just suggesting everything needs to be rewritten to be new. Also, standards are mentioned and referred to in this work, which I am guessing is due to the writer's experience as noted on the back cover. Not a negative to include that information, but I was not used to seeing specification notes in many of the traditional tech books I have read recently. The material for me was overall about how to talk about and work with REST concepts correctly. Semantics are addressed as well as when you would probably use this over that, etc. Guidance also seems helpful in sections such as "What Hypermedia Is For". I do appreciate code from the book being out on Github as well as on the book's website. While the examples are in Node.js at this time - it looks like the website is asking for different programming language ports-so examples have the potential to be added/ported over time. In summary, this book is for those looking to really take time and think about their APIs and if they are working with proper (or I guess one could only say proper in the authors' experience) REST techniques. If you need a quick tutorial to get from zero to done fast, this probably is not the material for you. As a side note, I found Appendix A and B as useful and quick references for HTTP codes and headers, but ymmv.

Overall conclusion: I would see this being a good fit for a REST fan who is trying to get even deeper into the proper way to complete their work.
Disclaimer: I got a copy of this book for review as part of O'Reilly blogger program.
10 of 11 people found the following review helpful
HASH(0x9b23fabc) out of 5 stars Great book on the future of the web Dec 4 2013
By Omar Diab - Published on Amazon.com
Format: Kindle Edition Verified Purchase
Fantastic book about hypermedia, a potential future for the web! I think this should be required reading for all API designers and consumers. It might not strike those who play fast and loose with code as very interesting, as its focused on good design rather than getting products out in record time, but I think it's something we should all follow.

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."

The book lays out the problems, solutions, and process of following good API practices clearly, as well as the kind of work that needs to happen to flesh out hypermedia. In this day and age I think anyone who is writing APIs should read this book first, for the betterment of all—programmers, users, and businesses alike.
4 of 4 people found the following review helpful
HASH(0x9b23dbdc) out of 5 stars Is decent reading, but not a very good reference June 11 2014
By Cresten St.Clair - Published on Amazon.com
Format: Paperback
How exactly does one write a book about complex relations between different resources, tell you to draw link relations, etc., yet fail to provide a single complete example of what he is talking about?

The maze example used throughout the book is contrived and confusing. It's useful for about the first few chapters, and quickly becomes too simple to reference.

I'm currently in the process of writing a web api, and it would be tremendous if I could have some more complete documents to refer to while I"m writing it.

The content is good, but it i severely lacking concrete illustrations / examples. Some complete examples in the appendix would be very nice.


Feedback