Product Details
|
While the REST design philosophy has captured the imagination of web and enterprise developers alike, using this approach to develop real web services is no picnic. This cookbook includes more than 100 recipes to help you take advantage of REST, HTTP, and the infrastructure of the Web. You'll learn ways to design RESTful web services for client and server applications that meet performance, scalability, reliability, and security goals, no matter what programming language and development framework you use.
Each recipe includes one or two problem statements, with easy-to-follow, step-by-step instructions for solving them, as well as examples using HTTP requests and responses, and XML, JSON, and Atom snippets. You'll also get implementation guidelines, and a discussion of the pros, cons, and trade-offs that come with each solution.
Subbu Allamaraju is a Principal Engineer at Yahoo! where, during the last one year, he has been developing standards and practices for designing RESTful Web APIs. Prior to that Subbu developed web services/Java based software and contributed to JCP and OASIS standards at BEA Systems Inc. Subbu has contributed to four books on J2EE, all published by Wrox. For a complete list of his works, and writings, see http://www.subbu.org/about.
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
5.0 out of 5 stars
A good book for novice and experienced web developers,
Amazon Verified Purchase(What's this?)
This review is from: RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity (Paperback)
This book simply describes the RESTful web design and semantics. By reading this book you will find the mistakes that even experienced web developers do and after reading the book you will find yourself at a different level of knowledge which will be very helpful in your next web development. I highly recommend this book to web developers who want to design and develop an scalable system.
5.0 out of 5 stars
Great condition, and arrived on time!,
This review is from: RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity (Paperback)
The book was in excellent condition, as described and it arrived on time as well. Will like to do business again!
Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta) Amazon.com:
4.5 out of 5 stars (11 customer reviews) 14 of 14 people found the following review helpful
5.0 out of 5 stars
Serious REST,
By J. Fahey - Published on Amazon.com
This review is from: RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity (Paperback)
As is common with O'Reilly's Cookbooks, the style of this book is very terse and to the point. There is not much handholding. The intended audience seems to be system architects who already know what they are doing, but who need to know what they should be aiming for when they want to be RESTful. The "recipes" in this Cookbook are more like Best Practices, since figuring out how to implement them is left as an excercise for the reader.Compared to my previous readings on REST, this book strongly emphasizes the use of consistent XML formats. For me, this was the most important lesson in the book. It is not enough to just use PUT and DELETE: in order to really think in terms of "representations," you need to design meaningful XML. Along these lines, Allamaraju's discussion of the Atom protocol is particularly interesting. 10 of 10 people found the following review helpful
5.0 out of 5 stars
Easy to read, packed full of details and great presentation.,
By Riyad Kalla - Published on Amazon.com
Amazon Verified Purchase(What's this?)
This review is from: RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity (Paperback)
I had been following "What is REST" tutorials online for the last few weeks as I was working on an API for an upcoming SaaS product. Unfortunately there were still some nitty-gritty details behind the tenants of RESTful design that weren't clicking in my brain, making it hard for me to really grok if I was following the intended design guidelines correctly or just faking it like so many other services do.Picking this book up after a recommendation from an HN reader, I got 4 chapters in before the smoke cleared in my brain and I had multiple "Ah ha!" moments such that the whole concept cleared up for me in a matter of days. It could be the writing style or presentation, but I just found it really easy to digest and answering all my questions as they popped up in my head. An excellent resource for anyone else working on RESTful API design. 8 of 10 people found the following review helpful
4.0 out of 5 stars
Good book to get up to speed quick on RESTful,
By Hugh Watkins - Published on Amazon.com
Amazon Verified Purchase(What's this?)
This review is from: RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity (Paperback)
I have not made it through the whole book, but my first impressions are really good. One of the interfaces we were designing for work is to time consuming to wait for a http response, in the first chapter of this book it gives you the way to do Asynchronous requests correctly with rest.There is also some good information on presenting resources that are not nouns, nouns are easy right you have a collection of people for example, you want to list all the people and do CRUD operations on a particular person. This to me is classical rest and is strait forward to do, but what about verbs (not in the POST, DELETE http sense) but in the give me driving directions sense. The book covers this and actually uses driving directions as it's example. There are a couple of issues I'm still trying to find covered in the book, like how to do pagination on a collection of resources correctly. There is at least one recipe on this, but I did not see how to indicate a default page size (ie I requested all user accounts, but only returned first 200 dues to size, how does the client know that 200 were returned) The other thing is the proper way to use http get parameters in search and other limiting operations. It would be nice to have some basic recipes there, but to be fair I might just not have seen them yet. All in all it's a nice addition to your technical library. |
|
|