|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
REST in Practice: Hypermedia and Systems Architecture
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| |||||||||||||||
Wird oft zusammen gekauft
Produktinformation
|
Mehr über die Autoren
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Produktbeschreibungen
Kurzbeschreibung
Why don't typical enterprise projects go as smoothly as projects you develop for the Web? Does the REST architectural style really present a viable alternative for building distributed systems and enterprise-class applications? In this insightful book, three SOA experts provide a down-to-earth explanation of REST and demonstrate how you can develop simple and elegant distributed hypermedia systems by applying the Web's guiding principles to common enterprise computing problems. You'll learn techniques for implementing specific Web technologies and patterns to solve the needs of a typical company as it grows from modest beginnings to become a global enterprise. * Learn basic Web techniques for application integration * Use HTTP and the Web's infrastructure to build scalable, fault-tolerant enterprise applications * Discover the Create, Read, Update, Delete (CRUD) pattern for manipulating resources * Build RESTful services that use hypermedia to model state transitions and describe business protocols * Learn how to make Web-based solutions secure and interoperable * Extend integration patterns for event-driven computing with the Atom Syndication Format and implement multi-party interactions in AtomPub * Understand how the Semantic Web will impact systems design
Über den Autor
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 Parastides is an Architect in Microsoft's Search group, working on semantics and knowledge representation technologies. Previously he was part of Microsoft Research where he led the design and implementation of a number of tools for scientists and a development platforms 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.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Kundenrezensionen
Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
19 Rezensionen
43 von 45 Kunden fanden die folgende Rezension hilfreich
Finally: an introduction to REST from the right perspective.
23. November 2010
Format:Taschenbuch
I started my REST journey with the two popular O'Reilly books ("RESTful Web Services" and "RESTful Web Services Cookbook") but found that they started a little too deep into the technical details and were missing the view from 30,000 feet. Sure, I learned stuff in those books about content type negotiation, the semantics of HTTP verbs and whatnot, but I was missing a really compelling answer to the question, "Why should I choose REST for my application architecture?".
At the same time I was reading about REST online and kept seeing lots of references to a mythical, magical thing called "Hypermedia As The Engine Of Application State" (HATEOAS) which lots of bloggers were effusive about but none of them could articulate very well. I was intrigued, but I wasn't convinced.
Luckily a colleague of mine mentioned this book to me and said it answered all of my questions, and he was right. Within a couple of chapters, it was obvious that the authors had made a real effort to explain not just what REST is but *why* it represents a significant shift in architectural thinking in software design. I quickly learned what REST really is and what it isn't. Most importantly I learned how it can be leveraged to build distributed systems that don't suffer from so many of the problems found with "classic" middleware technologies and architectures based on things like CORBA, DCOM, RPC, and so on.
After reading this book I returned to those two O'Reilly books and found they were much easier to follow and made far more sense. Having the architectural basis and benefits of REST explained properly by "REST in Practice" really accelerated my learning while reading those other books (which rely much more on code snippets and HTTP payload discussions rather than the underlying concepts).
If you're tasked with building a REST system or would like to figure out if REST is an appropriate approach for your designs, then this book is for you. If you're a script kiddie who just wants to learn how to write another Twitter client for the iPhone, this book may be overkill.
Building a RESTful system is much harder to do than simply consuming one that already exists. Designing a simple, usable RESTful system that properly follows the HATEOAS principle and remains easy for clients to consume is no small task either -- but this book helps immensely in that regard.
For making an architectural topic that is so poorly described elsewhere so tremendously easy to understand, this book easily gets five stars.
At the same time I was reading about REST online and kept seeing lots of references to a mythical, magical thing called "Hypermedia As The Engine Of Application State" (HATEOAS) which lots of bloggers were effusive about but none of them could articulate very well. I was intrigued, but I wasn't convinced.
Luckily a colleague of mine mentioned this book to me and said it answered all of my questions, and he was right. Within a couple of chapters, it was obvious that the authors had made a real effort to explain not just what REST is but *why* it represents a significant shift in architectural thinking in software design. I quickly learned what REST really is and what it isn't. Most importantly I learned how it can be leveraged to build distributed systems that don't suffer from so many of the problems found with "classic" middleware technologies and architectures based on things like CORBA, DCOM, RPC, and so on.
After reading this book I returned to those two O'Reilly books and found they were much easier to follow and made far more sense. Having the architectural basis and benefits of REST explained properly by "REST in Practice" really accelerated my learning while reading those other books (which rely much more on code snippets and HTTP payload discussions rather than the underlying concepts).
If you're tasked with building a REST system or would like to figure out if REST is an appropriate approach for your designs, then this book is for you. If you're a script kiddie who just wants to learn how to write another Twitter client for the iPhone, this book may be overkill.
Building a RESTful system is much harder to do than simply consuming one that already exists. Designing a simple, usable RESTful system that properly follows the HATEOAS principle and remains easy for clients to consume is no small task either -- but this book helps immensely in that regard.
For making an architectural topic that is so poorly described elsewhere so tremendously easy to understand, this book easily gets five stars.
11 von 11 Kunden fanden die folgende Rezension hilfreich
Solid Book for Learning about REST
21. November 2010
Format:Taschenbuch
This book provided a clear and concise overview of how to apply REST architectural principles to enterprise development. The books starts from the basics and in each chapter adds a new layer of sophistication to build a simple but complete business process with REST. I was especially interested in the sections that detailed how to use REST principles to handle enterprise integration tasks instead of using expensive proprietary middleware. I also liked the chapter on security which detailed how to use OpenID and OAuth to handle authentication and authorization respectively.
I would recommend this book to anybody looking for a good practical example of building a REST services.
I would recommend this book to anybody looking for a good practical example of building a REST services.
15 von 18 Kunden fanden die folgende Rezension hilfreich
Look at the Title
16. November 2010
Format:Taschenbuch
I read the comment about the "skip it" advice. I guess it applies to some people, but not all.
There is another book, the RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity (RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity) is an excellent book for the ones looking for quick recipes like the authentication. But that is a reference book, not a walk-through one.
If you like a book that walks through implementation of a simple REST service, discussing all the detail, pros, cons, going from an immature implementation to a more robust one, adding complexity, transactions, security and such, REST in Practice is the book. As the title implies, it is not a theoretic discussion, but a hands on explanation. It is a very small service, the book will not show a full blown, enterprise level system, as that is not the goal. It works on the tactical and implementation level. The code will not be usable for your own system in full, but the reader will certainly find some very good explanations and answers to general questions.
There is of course the need of an architectural level book about REST. This is not it. Hope O'Reilly will support one soon.
There is another book, the RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity (RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity) is an excellent book for the ones looking for quick recipes like the authentication. But that is a reference book, not a walk-through one.
If you like a book that walks through implementation of a simple REST service, discussing all the detail, pros, cons, going from an immature implementation to a more robust one, adding complexity, transactions, security and such, REST in Practice is the book. As the title implies, it is not a theoretic discussion, but a hands on explanation. It is a very small service, the book will not show a full blown, enterprise level system, as that is not the goal. It works on the tactical and implementation level. The code will not be usable for your own system in full, but the reader will certainly find some very good explanations and answers to general questions.
There is of course the need of an architectural level book about REST. This is not it. Hope O'Reilly will support one soon.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
