3 ms·
People really misunderstand REST, at least as in the original thesis. The original thesis was for the web. It was not meant for microservice JSON APIs. And th
by shp0ngle 5y ago
People really misunderstand REST, at least as in the original thesis.
The original thesis was for the web. It was not meant for microservice JSON APIs.
And the web is REST. HTTP, built for web, is REST. The REST principles are integrated in HTTP protocol itself, for I think two decades now.
The arguments "is this API RESTful" are nonsense.
...but yeah the article says the same, now that I actually read it.
...now, let's discuss what "agile" means. Or, maybe not.
- wingi 5y agoYes, REST is simple a sub-set of HTTP. Nothing more.
- zozbot234 5y agoThe article says otherwise, though. Using HTTP verbs properly is not sufficient for an API to be fully REST-based.
- ncphil 5y agoNo. Just no. It was the "branding" of Agile by consulting companies and publishers as a product they could sell is what got us into the sh*t show we're now in. Same has happened with REST and everything else the marketers touch. No. The _last_ thing we need is another vacuous rebranding. Unsurprisingly, most of the commentors here seem to get that, and are already calling out the b.s. when given the chance.