3 ms·
REST is one of the most blogged about, argued over bike sheds in tech. Once you stop agonizing over status codes, media types, routes being nouns, resources, et
by jeremycw 8y ago
REST is one of the most blogged about, argued over bike sheds in tech. Once you stop agonizing over status codes, media types, routes being nouns, resources, etc. it becomes surprisingly easy to be productive with HTTP. There are just a few simple rules to follow. GETs shouldn't make changes. PUTs should make idempotent changes. 2xx status codes are for success. 4xx and 5xx are for failure.
- naasking 8y agoSure, you can be productive by just using http as an RPC channel, but it's fragile. That's part of what REST covers.
- geezerjay 8y agoYou're describing RPC over HTTP. REST does rely on resources and does use a limited set of CRUD commands to operate over the resources, but REST also requires automatic discovery from a single starting resource/endpoint (see HATEOAS).