REST in Practice: Hypermedia and Systems Architecture and over 2 million other books are available for Amazon Kindle . Learn more
  • RRP: £28.99
  • You Save: £6.32 (22%)
FREE Delivery in the UK.
In stock.
Dispatched from and sold by Amazon.
Gift-wrap available.
Trade in your item
Get a £6.50
Gift Card.
Have one to sell?
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 in Practice: Hypermedia and Systems Architecture Paperback – 27 Sep 2010

See all 3 formats and editions Hide other formats and editions
Amazon Price New from Used from
Kindle Edition
"Please retry"
"Please retry"
£15.00 £15.16

Trade In Promotion

Frequently Bought Together

REST in Practice: Hypermedia and Systems Architecture + RESTful Web Services Cookbook
Price For Both: £38.60

Buy the selected items together

Trade In this Item for up to £6.50
Trade in REST in Practice: Hypermedia and Systems Architecture for an Amazon Gift Card of up to £6.50, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more

Product details

  • Paperback: 448 pages
  • Publisher: O'Reilly Media; 1 edition (27 Sep 2010)
  • Language: English
  • ISBN-10: 0596805829
  • ISBN-13: 978-0596805821
  • Product Dimensions: 17.8 x 2.5 x 23.3 cm
  • Average Customer Review: 4.7 out of 5 stars  See all reviews (6 customer reviews)
  • Amazon Bestsellers Rank: 218,040 in Books (See Top 100 in Books)
  • See Complete Table of Contents

More About the Authors

Discover books, learn about writers, and more.

Product Description

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

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

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.

Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

What Other Items Do Customers Buy After Viewing This Item?

Customer Reviews

4.7 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See all 6 customer reviews
Share your thoughts with other customers

Most Helpful Customer Reviews

2 of 2 people found the following review helpful By Paulo Sousa on 10 Sep 2011
Format: Paperback
Good book on practical REST.
It assumes you already know something about REST and its "philosophy" and presents the different aspects of REST with a single example that grows from chapter to chapter.
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
1 of 1 people found the following review helpful By A Reader on 19 Nov 2011
Format: Paperback Verified Purchase
I think it's fair to say that October 2008 was an important inflection point for many people's understanding of REST principles. It occurred when Roy Fielding expressed his frustration at many so-called "REST" services not embracing the hypermedia constraint. His blog post was entitled "REST APIs must be hypertext-driven", and when I first read it I didn't understand it. At all.

Since 2008 the world has been playing catch-up, and in terms of published books I would say that "REST in Practice" is the key book that provides would-be service designers with the full background they need to fully embrace REST, to be properly RESTful. And there are many benefits in doing so, as the book explains.

So this book is an essential read, basically. After reading it, and after thinking and considering and doing further research online, I went back to Roy Fielding's blog post from October 2008, and this time I understood it.

Although I regard it as essential, I dock a mark from this book because a) I disagree with the "in Practice" title, b) at times it's a tad verbose: less would have been more, and c) too much implementation code is presented for my liking, which wastes space. The real point of this book is to describe modern REST design; I felt the code was totally unnecessary.

So this book give the background understanding. Armed with that, I am getting great joy from using the "RESTful Web Services Cookbook" reference (also from O'Reilly). The Cookbook is the real "in Practice" book. Ironically the Cookbook has no implementation code... there's no need. Instead of code it has Recipes, and this approach works really, really well.

Any REST book from 2008 or earlier must be carefully evaluated in light of understanding the hypermedia constraint. For folk starting with REST, my advice is to start here with "REST in Practice".
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
4 of 5 people found the following review helpful By Nigel Small on 28 Oct 2010
Format: Paperback
REST in Practice should be on every software architect's bookshelf. It doubles up as both a well-thought-out tutorial and an indispensable reference to implementing RESTful web services. Pragmatically presenting its ideas in a such a way that does not favour a specific technology, it steps through many real-life situations and successfully manages to capture the original intent behind HTTP and the World Wide Web.

Fundamentally, this book throws open a window to an architectural style that there is little reason not to use when building distributed systems.
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