Fee Download The REST API Design Handbook, by George Reese
The benefits to take for reviewing the publications The REST API Design Handbook, By George Reese are coming to improve your life quality. The life quality will certainly not just regarding exactly how much understanding you will obtain. Also you read the fun or amusing books, it will certainly aid you to have enhancing life quality. Feeling enjoyable will certainly lead you to do something perfectly. Furthermore, the e-book The REST API Design Handbook, By George Reese will certainly offer you the session to take as an excellent need to do something. You could not be useless when reviewing this e-book The REST API Design Handbook, By George Reese
The REST API Design Handbook, by George Reese
Fee Download The REST API Design Handbook, by George Reese
The REST API Design Handbook, By George Reese. The established technology, nowadays sustain everything the human requirements. It consists of the daily tasks, jobs, workplace, enjoyment, as well as more. Among them is the fantastic web link and also computer system. This problem will certainly reduce you to assist one of your leisure activities, reading behavior. So, do you have ready to review this book The REST API Design Handbook, By George Reese now?
For everybody, if you want to start joining with others to read a book, this The REST API Design Handbook, By George Reese is much suggested. And you have to obtain the book The REST API Design Handbook, By George Reese right here, in the link download that we provide. Why should be below? If you desire other type of publications, you will constantly discover them and also The REST API Design Handbook, By George Reese Economics, politics, social, sciences, faiths, Fictions, and much more books are provided. These available books are in the soft files.
Why should soft file? As this The REST API Design Handbook, By George Reese, many individuals additionally will should purchase guide sooner. But, sometimes it's so far means to obtain the book The REST API Design Handbook, By George Reese, also in other nation or city. So, to relieve you in discovering guides The REST API Design Handbook, By George Reese that will support you, we assist you by offering the lists. It's not only the listing. We will provide the recommended book The REST API Design Handbook, By George Reese link that can be downloaded directly. So, it will not need even more times or even days to pose it as well as various other publications.
Accumulate guide The REST API Design Handbook, By George Reese start from currently. Yet the new way is by collecting the soft data of guide The REST API Design Handbook, By George Reese Taking the soft data can be saved or kept in computer or in your laptop. So, it can be greater than a book The REST API Design Handbook, By George Reese that you have. The easiest method to reveal is that you could additionally conserve the soft data of The REST API Design Handbook, By George Reese in your suitable and available gadget. This condition will certainly expect you too often read The REST API Design Handbook, By George Reese in the leisures more than talking or gossiping. It will certainly not make you have bad habit, yet it will certainly lead you to have much better practice to review book The REST API Design Handbook, By George Reese.
Designing and implementing web services APIs has become a common part of every software engineer's job. The RESTful approach to web services design is rapidly become the approach of choice. Unfortunately, too few people have truly solid REST API design skills, and discussions of REST can become bogged down in dry theory.
The REST API Design Handbook is a simple, practical guide to aid software engineers and software architects create lasting, scalable APIs based on REST architectural principles. The book provides a sound foundation in discussing the constraints that define a REST API. It quickly goes beyond that into the practical aspects of implementing such an API in the real world.
Written by cloud computing expert George Reese, The REST API Design Handbook reflects hands on work in consuming many different third party APIs as well the development of REST-based web services APIs. It addresses all of the debates the commonly arise while creating these APIs. Subjects covered include:
* REST architectural constraints
* Using HTTP methods and response codes in an API
* Authenticating RESTful API calls
* Versioning
* Asynchronous Operations
* Pagination and Streaming
* Polling and Push Notifications
* Rate Limiting
- Sales Rank: #112342 in eBooks
- Published on: 2012-06-04
- Released on: 2012-06-04
- Format: Kindle eBook
From the Author
I work with web services of all stripes every day. My Dasein Cloud Java libraries talk to AWS, Rackspace, the HP Cloud, Terremark, Savvis, Joyent, Eucalyptus, CloudStack, OpenStack, vCloud, vSphere, Nimbula, EMC Atmos, Microsoft Azure, and even more. Some are SOAP-based, some are just random HTTP query-based, and some attempt to be RESTful. Few actually are useful, and all have their warts.
I spend a lot of time on Twitter complaining about the things I don't like. When I asked my followers what I should write my next book on, the answer was overwhelmingly that I should write one on REST APIs. This book brings Fielding's theories on REST architectures together with my practical experience in cloud API consumption and development. My hope is that it will help API developers everywhere build truly RESTful APIs and understanding why REST constraints are important in the real world.
About the Author
George Reese is the co-founder and CTO of enStratus Networks, provider of cloud infrastructure management software for enterprise security, governance, and automation. At enStratus, he works with SOAP, REST, and other kinds of web services APIs on a daily basis. He is also the primary author of the enStratus REST API for accessing resources across multiple heterogenous clouds.
George holds an MBA from the Kellogg School of Management at Northwestern University in Evanston Illinois and a BA in Philosophy from Bates College in Lewiston, ME. He lives in Minneapolis, MN with his wife Monique and his two daughters.
Most helpful customer reviews
61 of 64 people found the following review helpful.
Mediocre on REST itself, dangerously wrong on crypto and security
By Marshall Pierce
The author has tried hard to make a useful reference on REST API design, and while certain parts of the book are acceptable, overall he has failed to provide a book that I would recommend to others as a guide. It is worth reading, but more as an opportunity for critique than as a source of gospel truth.
I'll start with the major issues and then proceed to smaller ones.
The author's coverage of security and how to use cryptographic primitives to handle request security is WRONG AND DANGEROUSLY INSECURE. Do not follow his advice on how to use SHA256 or anything else crypto-related; based on his suggestions he is not qualified to give advice on these topics. If you want to keep your API traffic secure, use TLS (properly configured -- see ssllabs.com for deployment best practices and a handy validator). If you cannot use TLS for some extremely good reason, you need to read "Cryptography Engineering: Design Principles and Practical Applications" (Ferguson, Schneier, Kohno) as an introductory text on designing cryptographic protocols. If that book hasn't persuaded you to simply use TLS and benefit from the hard work of experienced cryptographers, then it will at least give you a reading list of further advanced texts to refer to when designing your own protocol (which almost certainly won't be as good as TLS 1.2).
His coverage of authentication is correct in that it suggests using a finite-lifespan token. However, the fact that it does not cover OAuth 1 or 2 is bizarre for a book published in mid-2012. This is a serious omission since OAuth 2 (or 1) is likely to be a good fit for many modern REST APIs.
His coverage of HTTP PUT is incorrect. Using PUT to update part of a resource is WRONG as per the spec. See RFC 2616 9.6 ([...] for the RFC's coverage of HTTP PUT and RFC 5789 ([...] for HTTP PATCH. HTTP PUT may only completely replace the resource stored at a given URL, so his explanation of how to perform partial updates with HTTP PUT is not following the HTTP spec.
He does not cover matrix params at all, which is a shame as they are a useful option for doing pagination. His header-based approach is fine, but matrix params are right there in the HTTP spec as means of pagination.
His assertion that XML is better for large data sets due to easier streaming parsing is dubious. His recommended solution for JSON streaming involves generating invalid JSON. Streaming JSON parsers are no different from streaming XML parsers, and either format can be parsed in a streaming fashion.
I have other minor quibbles that I won't get into but they're just differences of opinion. The issues I've described above are basic factual errors or omissions.
0 of 0 people found the following review helpful.
Good read
By Wesley
Quick read with good insights on API design with a focus on restful APIs. Dig in and consider as inputs.
24 of 26 people found the following review helpful.
A good introductory read, despite minor liberties with rfc 2616
By maxbirkoff
This is a reasonable read for someone who doesn't know what REST is all about. Reese does a good job writing about the general nature of REST. Unfortunately there is some opinion mixed-in with fact, which makes it difficult for an inexperienced reader to tell fact from opinion.
The whole document has a somewhat informal tone; it reads like I'm listening to Reese talk to a friend. At times I find that makes for an easier read, and at times I find the lack of formality a little... grating.
Reese does not seem to like the idea of POST updating a resource, despite RFC 2616 reading "The actual function performed by the POST method is determined by the server and is usually dependent on the Request-URI." I don't honestly understand how Reese can argue for PUT updating a resource; RFC 2616 seems to me to imply that PUT will put a whole new version of an existing resource.
I wish Reese had spent a little more time talking about the effect of intermediate HTTP caches on API design; in particular POST and PUT invalidating intermediate caches for subsequent GETs is an important concept, as it forces the API designer to model consistent resources supported by separate verbs.
The REST API Design Handbook, by George Reese PDF
The REST API Design Handbook, by George Reese EPub
The REST API Design Handbook, by George Reese Doc
The REST API Design Handbook, by George Reese iBooks
The REST API Design Handbook, by George Reese rtf
The REST API Design Handbook, by George Reese Mobipocket
The REST API Design Handbook, by George Reese Kindle
Tidak ada komentar:
Posting Komentar