Interesting that REST and JavaScript ended up in the same graph.
So I reckon the REST is dominating the field, SOAP is on the way out and JavaScript is the little upstart that could?
I don't think the person writing this article has any grasp on what REST actually is. If they knew they wouldn't be comparing it to the "Asynchronous APIs". I use asynchronous API's everyday. And some of them are RESTful and I prefer them over those that are not.
I keep trying to read the article and I have huge problems. I recognize the words, but I have no idea what the author is trying to say.
The async api bit is pretty off for a couple of reasons.
1. REST is not inherently uni-directional. This is especially going to be the case in the internet of things, where you're just as likely to have servers on both ends.
2. You can do server->client push with Server-Sent Events.
So I reckon the REST is dominating the field, SOAP is on the way out and JavaScript is the little upstart that could?
I don't think the person writing this article has any grasp on what REST actually is. If they knew they wouldn't be comparing it to the "Asynchronous APIs". I use asynchronous API's everyday. And some of them are RESTful and I prefer them over those that are not.
I keep trying to read the article and I have huge problems. I recognize the words, but I have no idea what the author is trying to say.