- Paperback: 448 pages
- Publisher: O'Reilly Media; 1 edition (September 27, 2010)
- Language: English
- ISBN-10: 0596805829
- ISBN-13: 978-0596805821
- Product Dimensions: 7 x 1 x 9.2 inches
- Shipping Weight: 2 pounds (View shipping rates and policies)
- Average Customer Review: 42 customer reviews
- Amazon Best Sellers Rank: #84,302 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
REST in Practice: Hypermedia and Systems Architecture 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Frequently bought together
Customers who bought this item also bought
About the Author
Jim Webber is the SOA practice lead for ThoughtWorks where he works on dependable service-oriented systems. Jim was formerly a senior researcher with the UK E-Science programme where he developed strategies for aligning Grid computing with Web Services practices and architectural patterns for dependable Service-Oriented computing. Jim has extensive Web Services architecture and development experience as an architect with Arjuna Technologies and was the lead developer with Hewlett-Packard on the industry's first Web Services Transaction solution. Jim is an active speaker in the Web Services space and is co-author of the book "Developing Enterprise Web Services - An Architect's Guide." Jim holds a B.Sc. in Computing Science and Ph.D. in Parallel Computing both from the University of Newcastle upon Tyne. His blog is located at http://jim.webber.name.
Savas Parastatidis is a Developer in Microsoft's Technical Computing Cloud group, working on a platform for large scale data- and compute-intensive technologies. Previously he was part of Microsoft's Bing group where he focused on semantic and knowledge representation technologies. He also spent time in Microsoft Research where he led the design and implementation of a number of tools for scientists and a platform for semantic computing applications called Zentity. He originally joined Microsoft as part of the architecture team in the Connected System Division doing the initial work for the Oslo (M language) modeling platform. Prior to joining Microsoft, Savas was a Principal Research Associate at the University of Newcastle where he undertook research in the areas of distributed, service-oriented computing and e-Science. He was also the Chief Software Architect at the North-East Regional e-Science Centre where he oversaw the architecture and the application of Web Services technologies for a number of large research projects. Savas also worked as a Senior Software Engineer for Hewlett Packard where he co-lead the R&D effort for the industry's Web Service transactions service and protocol. Savas' blog is located at http://savas.me.
Ian Robinson is a Principal Consultant with ThoughtWorks, where he specialises in helping clients create sustainable service-oriented development capabilities that align business and IT from inception through to operation. He has written guidance for Microsoft on implementing service-oriented systems with Microsoft technologies, and has published articles on business-oriented development methodologies and distributed systems design - most recently in The ThoughtWorks Anthology (Pragmatic Programmers, 2008). He presents at conferences worldwide on RESTful enterprise integration and distributed systems design and delivery.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
This book has given me enough information to participate in the discussion, without "religious" fervor, and with some pragmatics, I hope. The book was not everything I had hoped for, (do I even really know what I hoped for), but was very good. I think I get it; HATEOAS, REST, and leveraging existing proven Web technologies and HTTP and ATOM. A suprise to me was how much I learned about HTTP; I knew nothing about it really, at a technical level. I never have had the need, so the HTTP information was good for me.
The next step for me is to evaluate existing "tooling" for REST support. In an MS .NET environment, WCF gives us great SOAP/WSDL/WS-* support, and this is a huge plus, despite my new understanding regarding the "shortcomings and wrong thinking" regarding the WS-* approach.
This was my entry point into REST, other than some good Wiki reads, and I would highly recommend it to others.
This book does get dirty, but it is at its best in provided slow, careful explanations of each step.
This is not a book that you will read in one night. Take your time, and the understanding will come.
After all, REST is much more than Remote Procedural Calls.
If you want to thoroughly understand REST, get and read this book.
The book builds up its description with great diagrams and code snippets (no pages among pages of code dumps yay!). The one are that I found not so useful for me was there was a fair amount of the book that was spent on ATOM syndication. While it was interesting I didn't really see the point of getting into that much depth for a book on Restful foundation. I might be more useful for someone else who is implementing something with ATOM feeds; for me its not the case. The other part was that there are examples in both .net and in Java. I think the author should of chose one language to stick with. I would say Java (or better yet in JRuby).
Other than that it was very well explained for anyone who wants to get a good overview and code examples on how to begin.
Most recent customer reviews
It was a dry read and I had to put it down, could not finish it.Read more