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
If your implementing web services, hoping to expose a REST (Representational State Transfer) interface AKA API (Application Programmer Interface), this book is for you. The knowledge present represents hard earned experience from a seasoned expert. I came across this right as I was designing a system and I agree with most of what the author has to say. I've even had some of my views cleared up. Well written and clear, you should check it out.
well written, however I don't agree with a lot of the conclusions as they are closer to most common misconceptions rather than doing a good job of clarifying them
Good content, some grammar issues. Good for those needing the knowledge of real REST vs. Plain http. A common smearing together of the two is not helpful. This book aims to alleviate some of that trouble.
The book is concise and helpful, especially for sharing important differences in common apis. I recommend this book to anyone interested in adding to his/ her knowledge of REST apis.
This is a good book if you’re already familiar with the basics of HTTP and are familiar with REST but want more specific recommendations.
I enjoy that the author goes through a few options at various points, weighing them. But I wish at times the author had been a bit more objective. I found continued references to enstratus a bit tiring. I’d rather know why the author thinks an approach generally applies.
A decent read..good for building concepts although a bit superficial on the authentication part. Should have covered more on the authentication part..but otherwise, pretty good
A short, quick read. I think it'd be good for a developer working on a REST API for the first -- or perhaps the first time professionally. Most developers with any real exposure to API development are probably going to find it obvious or superficial.
Of you are preparing to cerate new API service or you want to validate assumptions made in your current API project this book is for you. It talks about general REST requirements. I liked when author looked at different way of implementing API security or versioning mechanisms.
This book is short. Which makes it easy to read and quickly start using some of the ideas.
I lacked a little discussion about different REST approaches. Author mentions them but doesn't engage in discussion but maybe because of they you are getting nice coherent book about REST API design.
Overall good. Explains the difference between true REST and what is called REST APIs in the world. Why the limitations REST puts on the APIs are good, and what each means. Also covers some related topics such as Authentication, Paging/Streaming, etc.
Wish it went into more detail in some of the cases, especially with Authentication. The samples were not very friendly for an Ebook format.
In my opinion it’s too much preaching and too few reasons why we should follow the ideas of the author. He definitely has some good points, but they can’t really shine when it’s down to “follow me, I know what I do”. Explaining why the “normal” way doesn’t work would be a great addition for a second edition.