A lot of REST APIs out there are limited to
POST HTTP calls for
reading and modifying resources. This surely works for small projects,
but if you are about to design a long lasting API it can save you a
lot of trouble if you use the right method in the right situation.
Designing robust REST endpoints isn’t trivial, you always have to consider maintainability, scalability and performance. Wrong decisions in the latter often lead to problems with the other two. One of them is the inclusion of related resources or short IoRR (yeah, I made that up).
I bet you heard about server push in the last few months. Every HTTP/2 article mentions it, but do you really know what it’s all about? The intention of this article is to give you a kick-start into the topic.