PDF Download The REST API Design Handbook, by George Reese
Locating the right The REST API Design Handbook, By George Reese book as the best need is kind of lucks to have. To begin your day or to finish your day during the night, this The REST API Design Handbook, By George Reese will certainly appertain enough. You can simply hunt for the floor tile below and also you will certainly get guide The REST API Design Handbook, By George Reese referred. It will certainly not trouble you to cut your important time to opt for purchasing publication in store. By doing this, you will additionally spend money to spend for transport and also various other time spent.
The REST API Design Handbook, by George Reese
PDF Download The REST API Design Handbook, by George Reese
The REST API Design Handbook, By George Reese. Allow's review! We will frequently locate out this sentence everywhere. When still being a children, mom used to order us to consistently read, so did the educator. Some books The REST API Design Handbook, By George Reese are fully reviewed in a week and also we require the responsibility to support reading The REST API Design Handbook, By George Reese What about now? Do you still enjoy reading? Is reviewing only for you which have commitment? Definitely not! We below provide you a brand-new book entitled The REST API Design Handbook, By George Reese to read.
Why should be this e-book The REST API Design Handbook, By George Reese to read? You will certainly never ever obtain the knowledge and encounter without managing yourself there or trying on your own to do it. Thus, reviewing this publication The REST API Design Handbook, By George Reese is required. You can be great as well as correct sufficient to obtain exactly how crucial is reviewing this The REST API Design Handbook, By George Reese Even you constantly read by responsibility, you could support yourself to have reading book routine. It will certainly be so valuable as well as enjoyable after that.
But, exactly how is the method to get this publication The REST API Design Handbook, By George Reese Still perplexed? It matters not. You can enjoy reading this publication The REST API Design Handbook, By George Reese by online or soft data. Merely download and install guide The REST API Design Handbook, By George Reese in the link given to visit. You will obtain this The REST API Design Handbook, By George Reese by online. After downloading and install, you can conserve the soft documents in your computer or kitchen appliance. So, it will certainly alleviate you to review this publication The REST API Design Handbook, By George Reese in certain time or area. It might be unsure to appreciate reading this e-book The REST API Design Handbook, By George Reese, because you have whole lots of job. But, with this soft file, you could delight in reviewing in the leisure even in the gaps of your tasks in office.
Once a lot more, checking out habit will constantly provide valuable benefits for you. You may not require to spend many times to read guide The REST API Design Handbook, By George Reese Just set aside several times in our spare or leisure times while having meal or in your office to read. This The REST API Design Handbook, By George Reese will reveal you brand-new thing that you can do now. It will certainly aid you to enhance the quality of your life. Event it is simply a fun book The REST API Design Handbook, By George Reese, you can be happier and also much more fun to delight in reading.
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