Either there’s a giant „What’s the most stupid thing you could write about REST?“ contest going on this week or is this just uberawesome trolling? „REST is a hack on top of HTTP“ – Erm, What? Yes, someone really wrote that. 🤔🤦‍♂️
Give REST a Rest with RSocket bit.ly/2yHQHMn
11
15
2
57
“a huge drawback of REST is that it is text-based” – not sure whether to laugh or cry /cc @danielbryantuk

Oct 16, 2018 · 6:33 AM UTC

4
11
I'm not going to defend this one, as I reviewed it, rather than wrote it. Although I try and pick up factually incorrect information, I don't generally police opinion. I would recommend tweeting at the author for a discussion. I'm also always open to publishing a rebuttal?
1
1
I don't think it's about opinion here. It's more that a conclusion is completely devalued it it starts of with a factually incorrect premise. "… a hack on top of HTTP that was designed for sending books.", "text-based". That's just plain wrong.
2
Crying doesn't help. And I guess if you cry about stuff like that you won't ever be able to stop crying. Therefore laugh.
1
I guess I’m just used to a decent level of QA at @InfoQ.
1
Maybe it’s just a subtle way to ask for an audio book version of the thesis?
1
5
REST - means URLs, JSON, HTTP/1.1 - Graphs of microservices communicating would be better served not using something text-based. Using text is like running in debug mode. Why is it better using txt vs binary for services?
1
No. It does not mean that. Have you considered that the intercommunication between services might want to optimize for something different than performance? Especially if a goal of the overall system is independent evolvability of the individual ones?
1