Christopher Patti
1 min readJan 3, 2018

--

This is an excellent article. It has the punch of a rant but makes its case in a well reasoned detailed way with a lot of supporting evidence.

There’s one factor you don’t discuss though — tooling. People gave up on the paragon of logical purity that SOAP is or was if your article is to be believed, because if you weren’t doing your work in either Java or .NET the tooling was really, *really* awful. I’m told it’s gotten better, but when people feel pain they react to that pain by adopting new tools.

I get that your thesis is that we may have chosen an unfortunate path and should move on, but to what? You cite other more modern protocols, but I’d be curious about specific examples you can cite that could work as a direct replacement for either SOAP or REST.

--

--

Christopher Patti

Long time Boston area Husband, Freemason, and Geek (I chase bright shiny things! :) in that order.