REST API Design Rulebook and over one million other books are available for Amazon Kindle. Learn more
Buy New
$16.35
Qty:1
  • List Price: $19.99
  • Save: $3.64 (18%)
FREE Shipping on orders over $35.
In Stock.
Ships from and sold by Amazon.com.
Gift-wrap available.
Sell yours for a Gift Card
We'll buy it for $3.37
Learn More
Trade in now
Have one to sell? Sell on Amazon
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

REST API Design Rulebook Paperback – October 28, 2011

ISBN-13: 978-1449310509 ISBN-10: 1449310508 Edition: 1st

Buy New
Price: $16.35
26 New from $10.79 12 Used from $18.30
Amazon Price New from Used from
Kindle
"Please retry"
Paperback
"Please retry"
$16.35
$10.79 $18.30
Unknown Binding
"Please retry"
Free Two-Day Shipping for College Students with Amazon Student Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student


Frequently Bought Together

REST API Design Rulebook + RESTful Web APIs + RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity
Price for all three: $70.89

Buy the selected items together
NO_CONTENT_IN_FEATURE

Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Product Details

  • Paperback: 116 pages
  • Publisher: O'Reilly Media; 1 edition (October 28, 2011)
  • Language: English
  • ISBN-10: 1449310508
  • ISBN-13: 978-1449310509
  • Product Dimensions: 7 x 0.2 x 9.2 inches
  • Shipping Weight: 7.2 ounces (View shipping rates and policies)
  • Average Customer Review: 2.8 out of 5 stars  See all reviews (12 customer reviews)
  • Amazon Best Sellers Rank: #494,040 in Books (See Top 100 in Books)

Editorial Reviews

Book Description

Designing Consistent RESTful Web Service Interfaces

About the Author

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


More About the Author

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

Customer Reviews

This book starts with what REST API is all about.
Ayp
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.
JLangbridge
It appears to be an attempt to drag in some of the unnecessary complexity of SOAP with little added benefit.
Matthew Taylor

Most Helpful Customer Reviews

31 of 31 people found the following review helpful By Matthew Taylor on October 26, 2011
Format: Kindle Edition
The first chapters give a good feel for the vocabulary, and some good techniques for implementing REST. A lot of the 'rules', especially those related to basic CRUD operations, are clean and simple with useful examples.

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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
23 of 23 people found the following review helpful By Isteve on November 14, 2011
Format: Paperback
Even though this book only contains 114 pages, it took me forever to work through it, mostly because it reads like a high school text book from the 50's, and spends way to much time trying to explain "WRML" a standard the author tries to enforce even though in my last 5 years of working with REST services I've never encountered this "standard" and it just seem to be over kill as REST is suppose to simplify we services.

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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
8 of 8 people found the following review helpful By T. Epstein on March 28, 2013
Format: Paperback
This book has been criticized by most reviewers because of its focus on Web Resource Modeling Language (WRML). The author, Mark Masse, defines and documents WRML as his specific example to satisfy the general rules and design goals he catalogs in the book.

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.
1 Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
8 of 9 people found the following review helpful By JLangbridge on February 2, 2012
Format: Kindle Edition
Disclaimer: I was given a free copy to review.

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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Recent Customer Reviews


What Other Items Do Customers Buy After Viewing This Item?