Friend Reviews
To see what your friends thought of this book,
please sign up.
This book is not yet featured on Listopia.
Add this book to your favorite list »
Community Reviews
(showing
1-30
of
57)
The book tries to establish a set of rules for REST interfaces - I'm OK with that, it's what its title says. When you define rules, you take an opinion, that's fine. And most of what is defined as a rule is something I'd support as a good practice. A possible benefit of this rule book would be to provide some compact, memorizable, and clear guidance on good practices.
But then there's this obsession about WRML.
WRML is a proposed way of defining the content types and schemas of REST APIs - see ht...more
But then there's this obsession about WRML.
WRML is a proposed way of defining the content types and schemas of REST APIs - see ht...more
If you're new to the world of REST APIs, and if you're looking for a good set of working rules on how to design them, then Mark Massé's REST API Design Rulebook should live up to its title just fine. It's a short book (you could read it in an afternoon) and it tackles the subject matter in a direct and orderly fashion. It starts with a brief history lesson, quickly reviewing the history of the world wide web, of HTTP, and of the emergence of the whole notion of "RESTful" APIs and services. From...more
This is a better book than my pure star rating would seem to indicate. It's not that I didn't like the book - it was OK.
However, as a highly opinionated book, I wonder how widely accepted the ideas being laid down as rules actually are. I think there is much here that people can agree is best practice when designing a RESTful API. However, I'm left with the feeling that much of the rest of it is a one-man campaign towards standards that may never be adopted at large.
So, reader beware: I suspect...more
However, as a highly opinionated book, I wonder how widely accepted the ideas being laid down as rules actually are. I think there is much here that people can agree is best practice when designing a RESTful API. However, I'm left with the feeling that much of the rest of it is a one-man campaign towards standards that may never be adopted at large.
So, reader beware: I suspect...more
Two huge problems with this book. It's short and very repetitive so the information content is about a couple of blog posts. The 'rules' are highly subjective, and much of the book is pushing the author's WRML 'standard' which I've never seen in the wild. The only real positive is that it's a comprehensive survey of the issues you need to think about when designing a REST API: just don't take the rules as gospel and research best practice from major APIs so you understand the context.
Jun 16, 2013
Clayton Lowell
is currently reading it
Jun 12, 2013
Henry Suryawirawan
marked it as to-read
May 26, 2013
Nycholas Oliveira e Oliveira
is currently reading it
Apr 23, 2013
Marc
is currently reading it
Apr 10, 2013
Pieter
marked it as to-read
Mar 18, 2013
Shu Liu
marked it as to-read
Mar 14, 2013
Jack
added it
Feb 08, 2013
Gavin Phoenix
marked it as to-read
Jan 24, 2013
Robert
marked it as to-read
Nov 29, 2012
SnowDevil
marked it as for-reference-only
There are no discussion topics on this book yet.
Be the first to start one »

view 2 comments

















