Enviar a

Nicaragua

Hola

Iniciar sesión

Carrito

Internal test

Rastrear paquete

Assistant

Descargá el app

REST API Design Rulebook | Envi

Joey G
19 de agosto de 2025
Buy now
Very informative and precise
kontakte
2 de noviembre de 2014
Great set of rules, just ignore the parts about WRML of you don't want to use it
I think this is a great book for people who already have REST experience, but need some guidelines for building their services. I lead a services design and development team and we're planning to use most of these rules as standards.The one issue I have with the book is its use of WRML. While you can ignore the constant mention of WRML and still benefit from the book, it does get to be a little much. This wouldn't be a huge issue if WRML were a fairly well adopted standard, but it's not.To get around this, I simply read all of rules and tried to learn the concept/essence of the rule of it used WRML. Most of them used it as a suggested implementation of the rule, so it wasn't difficult to do.Ver másVer menos
2 personas la encontraron útil
simerai
26 de noviembre de 2012
Great book
I really appreciate the pragmatic approach to REST API's. I look forward to more books like this one. The book really helped my understanding of REST and web API design in general. easy read.
Michelle
16 de febrero de 2017
Pretty good when you ignore the WRML parts, but what's left?
Agree with what others say about WRML. While WRML does seem to have some interesting uses as a standard, it clearly isn't a standard yet (google it and you will only get references back to the book and the author). For a book that is purporting to be a rulebook for design, promotion of a non-standard protocol is counterproductive. There are some good tidbits in terms of usage of headers for descriptive purposes and keeping urls and body mostly for content. However I found myself skipping over parts related to WRML more than I was actually reading the book.Ver másVer menos
8 personas la encontraron útil
Gabriela Segura Guzmán
26 de abril de 2019
Contenido
Nada
Reese Wilson
1 de septiembre de 2015
Great for designing *true* REST APIs (aka hypermedia APIs)
It is unfortunate that "REST" has different definitions, and this may be part of the reason this book has gotten poor reviews. The author does briefly mention that he fills in the gaps missing from current recommended best practices, but the significance is understated. See http://blog.steveklabnik.com/posts/2012-02-23-rest-is-over for more about the completely different meanings.The rules in this book are well thought-out solutions to constraints which are rarely addressed. A subset of them will appeal to people trying to write a 'REST' API based on their existing definition, but they may rebel against the added complexity related to media types such as WRML. As for WRML itself, it is just one example of how to meet the constraints of REST such as HATEOAS. The principles can obviously be extrapolated into your own solution. The principles used in the WRML solution can be invaluable in transforming a traditional RPC API into a true REST API.If you are not designing your own general media type to be used across organizations and problem domains, or unless you want to use the imaginary (as far as I can tell) WRML media type, you can probably skip chapter 5. The relevance is limited to a very niche audience. You can usually either create and document your own domain-specific media type, or use a well-known type (e.g. JSON-LD, Siren, HAL, JSON API, Collection+JSON).Complaints about the inclusion of WRML media type details may be well founded, but the ideas behind this media type should definitely not be dismissed. As far as examples of good APIs, Twilio's API uses a media type that follows some of the principles behind WRML, and Github's uses a bunch as well.Ver másVer menos
1 persona la encontró útil

Ver más reseñas

Otras opciones

REST API Design Rulebook

Reseñas

Buy now

Great set of rules, just ignore the parts about WRML of you don't want to use it

Great book

Pretty good when you ignore the WRML parts, but what's left?

Contenido

Great for designing true REST APIs (aka hypermedia APIs)

También te puede interesar

También te puede interesar

Otras opciones

REST API Design Rulebook

Reseñas

Buy now

Great set of rules, just ignore the parts about WRML of you don't want to use it

Great book

Pretty good when you ignore the WRML parts, but what's left?

Contenido

Great for designing *true* REST APIs (aka hypermedia APIs)

También te puede interesar

También te puede interesar

Great for designing true REST APIs (aka hypermedia APIs)