reviews
Oct 11, 2008
Everything from OREILLY is of the highest quality. The book as you would expect is heavily biased toward REST versus an RPC architecture. I agree that one must read this book if they hope to understand all of the options in building scalable web-services.
0 comments
like
(1 person liked it)
May 23, 2009
This is both a manifesto for what the authors term 'REST-Oriented Architecture' (ROA), and a technical dive into the mechanics and semantics of REST. It comes as a big breath of fresh air after years of being harangued by the putative benefits of Service-Oriented Architecture (SOA) with its plethora of web-service standards centered on XML, SOAP, and WSDL, and the many competing and largely incompatible SOA toolkits.
REST (or ReST) stands for 'Representational State Transfer', a term More...
REST (or ReST) stands for 'Representational State Transfer', a term More...
Nov 17, 2008
Overall, I really liked this book. It has gotten me excited about REST and Resource Oriented Architecture as a driving force for the programmatic web. I would recommend this book to anyone interested in learning about those topics.
On the other hand, I found the author's use of the first person "I" to be somewhat jarring, especially the fact that they repeatedly felt the need to re-emphasize that the information presented was "only their opinion and not hard and fast More...
On the other hand, I found the author's use of the first person "I" to be somewhat jarring, especially the fact that they repeatedly felt the need to re-emphasize that the information presented was "only their opinion and not hard and fast More...
Apr 06, 2009
A great resource that explains why - and how - to keep web services as simple and meaningful as possible. Web authors are encouraged to keep the Resource in URLs - those "things" we are interested in -, rather than cluttering the developer mindspace with an ever-growing pile of verbs and extra protocols.
Having developed with REST style as well as Big Web Services, this book made it clear to me just why I prefer the former.
Having developed with REST style as well as Big Web Services, this book made it clear to me just why I prefer the former.
Nov 26, 2011
This book seems to be THE book to read if you want to really dig in to REST. I absolutely love the authors' Resource Oriented Architecture and how much their presenting it points to the abuse of the word "RESTful". However, I was disappointed in how one or two of their examples didn't quite meet all the criteria of ROA! With that said, I love theory and will undoubtedly continue to reference this book in my career.
If you want excellent commentary on Roy Fielding's disser More...
If you want excellent commentary on Roy Fielding's disser More...
Mar 25, 2008
REST REST REST. Everyone is talking about RESTful webservices, and there is some merit to the discussion. This was a very well thought out book and presented the REST topic in a sensible light. The only problem that I had was that the book could have been written in 200 pages, maximum. Aside from that, it is worth a read, especially if you want to learn more about REST and its philosophy. In a nutshell, REST involves taking a webservice that looks like
http://domain.com/service?target=somethi... More...
http://domain.com/service?target=somethi... More...
Jan 06, 2011
This book is rather great. The concepts of RESTful architecture are very straightforward, and reading this book makes you realize that simplicity in integration and service calls brings simplicity and elegance to your systems design.
Jul 10, 2010
Too long, with many not necessary (imho) details. Although there are chapters, that provides good description of REST concepts & how to design REST services
Sep 11, 2009
I love restful web services. "The web as it should be used" is theoretically marvelous but practically difficult to do. This book will get you more excited about REST and help you a bit further but we still aren't there.
Feb 08, 2011
Book was good. Too much preference was given to Ruby/Ruby-on-Rails for my taste and according to the author's original intent.
Oct 29, 2007
not bad, but REST probably doesn't need a whole book. anything that has examples in 3+ languages is just trying to make a broad topic seem practical. nice coverage of what works and doesn't work, though, and general design suggsestions
Jan 28, 2008
This book while interesting, leaves much to be desired. They author is a bit scattered, and following his examples and code snips is a bit trying at times. None the less, it is an interesting read on REST style development.
Nov 22, 2008
Thorough and at times tedious look at REST-based services. It does cut through the hype and explain the benefits of REST rather well, though.
Aug 25, 2008
Not sure I'll follow all of his suggestions, but definitely worth reading. I enjoyed the exposure to new concepts.
Nov 22, 2011
Finished the Old Testament of RESTful Web Services. I feel a little traumatized.
Feb 09, 2012
Feb 05, 2012
Feb 05, 2012
Feb 03, 2012
Feb 02, 2012
Jan 31, 2012
Jan 31, 2012
Jan 30, 2012
Jan 27, 2012
Jan 27, 2012
