The article ignores the fact that you can have use case specific resources and/or views with REST, too. If you're only interested in a picture and a title from

The article ignores the fact that you can have use case specific resources and/or views with REST, too. If you're only interested in a picture and a title from a book, you could crete a content type that includes just that. And advantage of this approach is, that you can tailor the database query to return just that, what is not directly possible at the abstraction level of GraphQL.