GraphQL API Design (API-University Series Book 5)

What could be better than a book that is both comprehensive and short? This excellent introduction to GraphQL manages to squeeze everything you need to know to get started into just 83 pages. If they sold books by the pound, this would be expensive indeed, but I buy my books by the ability to teach me something without wasting my time, and in that case, this book is a bargain.That said, I'm a .NET programmer, and so after reading the first 2/3, I switched to reading the documentation for HotChocolate, so that I can write in C# rather than <bleh> JavaScript.In any case, this "pamphlet of a book" is highly recommended.Oh, PS: this book works well on the Kindle as well.

I think it is better if the author should add more examples.

As current spec, the implementing type will not automatically contain the fields defined in the interface. This author don't have the real GraphQL implementation experience.

I'm learning about GraphQL for the first time, and so this book offered a good introduction for my needs. That said, at only 86 pages (and physically small pages at that) it's barely a book - more of a cheatsheet or CliffsNotes reference for GraphQL. Everything in this book is most certainly available on the web with a little diligent Googling. That said, I like physical books I can pull off the shelf when I need to, and this is one I expect I'll refer to often in the future when I need a quick reference to something as I continue to learn GraphQL.

I enjoyed this quick introduction to Graphql. It is sufficient to get anyone up and running with the technology and the concepts which are different than REST.

You would learn more simply reading the spec. This isn't a book it is a pamphlet.

An excellent read.

£30 for effectively 72 pages (once you've removed the table of contents, the blank pages and the pages advertising the author's other books in the "API University" series) is outrageously over-priced for what is presented here. There's a lot of "generalization" padding going on even with this low a page count. Given the paucity of GraphQL books on the market others may find this book (I'd describe it more as a pamphlet!) more useful than I did, but my advice would be to try and peruse a copy before parting with your money. The other four volumes in this API series, sadly, are not much different and to me there is a certain irony (if not a falsehood) in implying that the five books in this series constitute an "API University" given how slim each volume is, Have our universities really fallen to that low a standard? The dull writing style does recall that of an academic white paper, so maybe that's the reason for the nomenclature.