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
SrcMaker
8 de noviembre de 2015
A good overview of the REST Protocol
It is not really a book that gives you copy and paste copy examples. If this is what you are looking for to quickly hack up REST web services look elsewhere. I think this book gives the uninitiated a thorough and concise overview into the intentions of the REST protocol. As the creators of REST intended REST itself is very much opened and as development manager I see many web services that claim to be REST really not follow w the REST protocol but instead are simple HTTP based APIs that can be called via REST client implementations such as JAX-RS. Which I guess is fine, all depends how much of a purist you are to follow standards.Ver másVer menos
DCM
12 de diciembre de 2012
Some basic structural ideas + some debatable formatting suggestions + an attempt to codify REST before CORS is a standard.
This was a very quick read which focuses mostly on recommendations for the structure of a RESTful system.There were some good ideas for people starting their first RESTful system, but this isn't exactly a codified type of system by its very nature. He did put some ideas together for his own standardization, but I didn't really find them to be at the point where I'd change any of my existing code.The best design appears to be extremely simplistic, whereby you have a root, then collections, then records, then functions, where you then execute your CRUD expressions.He recommends (as most developers would) that you use the correct CRUD expression for the correct job rather than using parameters. So, you'd have:[...]rather than[...]And use the type DELETE to say that it's a delete. This is easy if you are using something like curl to effect the action, but in the web-world, we're stuck with security issues that cause this to be impossible.From an AJAX call, I can't execute a DELETE function. Moreover, unless I'm using something like CORS, I can't do a cross-domain post unless I'm using JSONP, which only accepts GET.(JSONP & CORS are another book altogether!)In any case, if you want to make things both RESTful and work in real life, you need to use ALL GET STATEMENTS.Yes, it's horrible and awful and messy, but it works. In 5 years, we may have CORS to the point where it is functional on all browsers, but right now it isn't.Another issue I noticed was the insistance on only using paths to execute calls, and including the requested return type in the paramenter. So, to get myrecord I'd do this:[...]or[...]Well, I happen to do this:[...]It is bad form to include the script, but in the real world, you can put together these generic handlers very quickly and they are quite effective. Moreover, they require absolustely no setup or configuration. I can give a 15yr old programmer a generic handler and they can have it up in seconds. All our databases are cloud systems (either Amazon R2 or Azure) so, we pop those handlers on a fat set of machines and we don't worry about losing a tiny bit of efficiency. HOWEVER, if you're going to be doing a lot of work with client-side applications, you really should be using an MCV4 app to serve it. If you are a web-app company, and have a bunch of engineers who live in a .Net web form world, stick with the handlers, that way you can leverage existing personnel.As far as this book, I was looking for some better ideas with more detail as to the best way to set up these interfaces so they can "start" with JSONP and then be converted over the CORS at a later time. We work in constant flux and REST is moving too fast to formally codify until CORS support covers 99% of the market.
Albertazzi Angelo
13 de julio de 2022
Datato ma ancora utile
Libro datato che però contiene alcune best practices per quanto concerne l'implementazione di Web Api Rest. Visto il costo ne valeva la pena.
Sudhir Giri
24 de octubre de 2016
Nice book
Most helpful
james
14 de enero de 2016
It is the best boon on rest APIs I have read
I am a web developer and read this hols a few years back now. Since then everyone on my team has read it. It is the best boon on rest APIs I have read. It is short, fundamental and very easy to digest. Great book.
Ricardo
9 de junio de 2018
Nice
Good contentUsefulVery useful on the understanding and the design of your APIRest could be use on many technologies
Anis Ben Ghanem
8 de abril de 2024
As described
As described

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)

A good overview of the REST Protocol

Some basic structural ideas + some debatable formatting suggestions + an attempt to codify REST before CORS is a standard.

Datato ma ancora utile

Nice book

It is the best boon on rest APIs I have read

Nice

As described

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)

A good overview of the REST Protocol

Some basic structural ideas + some debatable formatting suggestions + an attempt to codify REST before CORS is a standard.

Datato ma ancora utile

Nice book

It is the best boon on rest APIs I have read

Nice

As described

También te puede interesar

También te puede interesar

Great for designing true REST APIs (aka hypermedia APIs)