3 ms·
Isn't all of that just dogma? See https://news.ycombinator.com/item?id=276687 https://news.ycombinator.com/item?id=276687 for further explanation.
by johansch 11y ago
Isn't all of that just dogma?
See https://news.ycombinator.com/item?id=276687 https://news.ycombinator.com/item?id=276687 for further explanation.
- DomreiRoam 11y agoUsing an architecture shouldn't be a dogma but a choice. REST is defining a set of constrains that provides a set of benefits. REST emerges because people noticed that the 'Web' was more scalable and robust than other distributed architecture (COBRA, DCOM...). So if your usecases would benefits from caching, discoverability... then you may want to choose REST.
- zeveb 11y agoReading that old thread really makes me realise how perceptions have changed over time. I think more folks understand how useful REST can be, as it provides a standard set of semantics for talking about resources, and that semantics are pretty widely applicable across various situations. In that respect, REST is a lot like relational calculus: certainly not a panacea, certainly not universally-applicable, but an extremely useful way to approach a large number of different problems. And just as one should have to justify why one is not using an RDBMS (and there are a huge number of reasons not to!), one should need to think hard before abandoning REST for RPC.