Paul Grenyer

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resources

James S. A. Corey ISBN-13 ‏ : ‎ 978-1841499932 Abaddon's Gate takes a while to get going. About half the book to get going. It’s all new character introductions and building. The second half is more exciting, but drawn out. Chrisjen Avasarala is totally absent and I’d like to have understood more about where the ring came from and what its purpose was. I guess that’s to come. Inevitably the further divergence of the TV series from the books became more apparent. The TV series appears to have merged and changed a lot of the characters, missed out and changed a lot of the story, but brought it back to mostly the same point. Let’s hope the next one improves.