3 ms·

I think this is a version of the right answer. I would love to see someone do a teardown of all of the Best in class REST interfaces. Because the reality is som

I think this is a version of the right answer. I would love to see someone do a teardown of all of the Best in class REST interfaces. Because the reality is some of the systems that get pointed to as most robust and we'll designed generally all contain a place where they have heavily skewed from the standard. All that being said I think REST is an architectural pattern that can bring some order to the chaos. And I have seen thought experiments experiments that embrace it's constraints bring significant performance enhancements to many a system.

munk-a 8y ago
I've worked with systems that use RESTish patterns purely for request pattern conformity, eschewing any of the auto-discovery portions. I've found that reliance on verbs for noun modification with some separate action verbs builds a system that is very clean to interact with but... it's all in the details, there are plenty of terrible RESTish systems out there and there are some wonderful systems built on alternate patterns (like XML RPC). I think the one thing RESTish design can bring is a simplification to the communication layer, but if you're interacting with it through HTML forms then you'll need hacks to get it working in the first place (many HTTP verbs are not supported as methods by most browsers). Basically, it's an additional tool with some value for organization, if you use it zealously you can waste years of labour building a perfectly RESTful system. Do what works for you.