3 ms·
I prefer REST because one way fits all usages: GET /resources, POST /resources, GET /resources/id, PUT /resources/id, DELETE /resources/id Five routes for one
by joshguthrie 11y ago
I prefer REST because one way fits all usages:
GET /resources, POST /resources, GET /resources/id, PUT /resources/id, DELETE /resources/id
Five routes for one resource type. If you need more resources, you nest your URIs. Why would you need POST /deleteResource?idRes=id when you can just DELETE /resources/id?
Code reuse wins.
- augustl 11y agoIMO the biggest challenge here is cases that doesn't fit in. What if you want to create or update multiple records in a single operation, for example. There are ways, namely additional batch resources, but structuring that is your problem.