> Devs need protocols and specifications, not vague > architectural ideas that leads to "you're doing it wrong" > blog posts. This is precisely it. If an inte

> Devs need protocols and specifications, not vague > architectural ideas that leads to "you're doing it wrong" > blog posts. This is precisely it. If an integration mechanism can't be implemented as a clear and uncomplicated library that strongly encourages correct use by making it the path of least resistance, it probably isn't any good. (And note that I said "library" rather than "framework". This is important as libraries are more like a thin layer of glue while framework is more like a metastasising cancer) Most of the time, REST, strictly speaking, demands too much attention even for relatively simple stuff, and therefore is not a good integration technology. However, some adaptations of REST are. The one thing that is a bit sad is that there is some nomenclature confusion. These days a REST API doesn't refer to Fielding's vision, but a more practical adaptation of the mechanical bits of it.