- Taschenbuch: 112 Seiten
- Verlag: O'Reilly and Associates; Auflage: 1 (21. Oktober 2011)
- Sprache: Englisch
- ISBN-10: 1449310508
- ISBN-13: 978-1449310509
- Größe und/oder Gewicht: 17,8 x 0,6 x 23,3 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 50.701 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
REST API Design Rulebook (Englisch) Taschenbuch – 21. Oktober 2011
|Neu ab||Gebraucht ab|
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Über den Autor und weitere Mitwirkende
Mark Masse resides in Seattle, where he is a Senior Director of Engineering at ESPN.Mark has fourteen years of engineering, management, and architecture experience with The Walt Disney Company. He began his career with Starwave creating rich, interactive Java applets for ESPN Sportszone, NFL.com, and NASCAR Online. Mark architected and developed the content management system (CMS) that powers all of the Disney web sites including ESPN.com, ABC.com and Disney.com. In 2008, he received a "Disney Inventor Award" for creating a "System and Method for Determining the Data Model Used to Create a Web Page."
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Unfortunately, the later chapters get more and more focused on specifying something called 'WRML', which is a concept/language newly introduced in this book as far as I can tell.
Personally I would recommend ignoring the sections dealing with WRML (or keep them in mind as a detailed example of one possible way of handling some of the REST issues).
As to WRML itself: yuck. It appears to be an attempt to drag in some of the unnecessary complexity of SOAP with little added benefit. Not recommended.
Overall: There is some definite value to be found in this book, just be wary and realize some of this is the author's attempt to 'create' a new standard as much as explain the current state of the art.
There were a couple of interesting chapters (All the ones that didn't focus on "WRML") I particularly enjoyed chapter 3, explaining what HTTP status codes to use in case of errors as this is the most complete list I've found till date.
If you are new to REST I would recommend that you look to another book as this one might just confuse you with the "WRML Standard" that you won't see out in the real word. If you have been working with REST some time and just want something to fall back on when you are uncertain of something, this could come in handy once in a while, but then again so could Google.
Still, I think this is useful because it's a very sincere and thorough attempt to apply the principles of REST, and satisfy REST constraints, in a general way that could be used for a lot of different services and applications.
Roy Fielding, who wrote the REST dissertation, can be difficult to read and understand. Fielding speaks almost entirely in abstract principles and rules, sets a very high bar for RESTful designs (particularly w.r.t. loose coupling), and levels harsh criticism against implementations that don't meet that bar. He is not very helpful towards developers and API designers who struggle with real-world questions of how to interpret and apply REST principles in their services and applications.
Masse is really trying to bridge the gap between REST theory and practice. He is aggressively uncovering questions and issues, and he provides his own answers. At a minimum, this is a really interesting case study that deserves careful evaluation and discussion.
His treatment of media types, link relations and schemas is an important example of this. REST demands a systematic use of media types to formalize the expectations between client and server components, but the literature is really silent on *how* media types are supposed to be specified, and how clients are expected to consume and adapt to this critical metadata. Whether you like or don't like the way Masse answers these questions in the context of WRML, the underlying questions, issues and design criteria are important, and need to be explored.
I've been using the REST interface for some time now, but on and off, and I'm not necessarily an expert on the subject. I wanted, I needed, something that could help me fully use REST, and explain the little details that I probably missed. I needed something to help me fully grasp REST. I thought that this book would be the answer.
The author obviously had a very good grasp on the technology, and knows his subject. The very first pages are about the history of REST, where and why. Very quickly, the author talks about WRML, a conceptual framework he invented. Unfortunately, we go into fat more detail about WRML than we do about REST. There are REST rules, and they are very good, but they are often drowned out by WRML. Specifically, when talking about the importance of JSON, the author correctly states that JSON is important, but cannot do everything, therefore here is what can be done with WRML. The book still contains great rules on REST, but you have to filter them out, which is a shame.
The title may have been misleading, or possibly I was thinking too much about one particular subject, but this was not quite what I expected. I thought that this book would be readily available every time I create a REST interface, but instead, it may just return to the bookshelf to be rarely used.
For me, the highlight reel included: the first three chapters (on identifier design, interaction design, and metadata design), and some of the discussion in the final chapter ("Client Concerns") about security, and the overview (however brief) of JSONP and CORS as solutions for some otherwise challenging situations.
The two bits where it went off the rails a bit for me:  Any of the discussion of between-document linking--I haven't encountered this much (at all?) in the real-world and a lot of it seemed overkill to me, to go into that depth on how to link documents from within the API. (And as an aside, it was very unclear to me how the 'rel' (relationship) attributes were to be defined.)  WRML: what? Even after reading the whole book, I was still left wondering what exactly WRML was intended for, and what it would buy me as a developer. It seems that Massé wrote this book in part to evangelize this framework, but I could not quite get my mind sufficiently around it to say that I got it.
On the other hand, Massé does a great job with the "rules" (again: especially in the first half of the book) and I would recommend this to anyone that needs an introduction to REST API design. That being said, after absorbing this one, you'll probably want to explore further with one of the other O'Reilly books on the subject, and/or find yourself a couple of resources on OAuth.