REST API Alternatives
blog.programmableweb.com
REST API Alternatives
1–10 of 82 posts
Re: REST API Alternatives
#2If he's making the claim that "there are a number of initiatives, technologies and discussions that are starting to nibble at the crust of the de-facto standard that REST has become.", then surely he would have evidence of this claim?
To start with:
1. Label your axis, that graph doesn't say anything.
2. Maybe we should be looking at percentage change in the graph rather than whatever is being graphed here.
Re: REST API Alternatives
#3RESTful services still work in those situations where they are correctly applied. Maybe what has happened is some of the less mature and more shrill developers have stepped back from their war on any Web service that doesn't fit their dogmatic rest-tard view of the world. There are plenty of valid XML-RPC based services that continue to run well despite the whining that someone somewhere did not yet have a ruby gem to connect their ruby on fails site to it and that it was simply unacceptable - and so complain on twatter they must!
So in short - no, REST works, use it in the right places, and remember kids - not every Web service or endpoint has to expose a REST based interface.
Re: REST API Alternatives
#4If he's making the claim that "there are a number of initiatives, technologies and discussions that are starting to nibble at the crust of the de-facto standard that REST has become.", then surely he would have evidence of this claim? To start with: 1. Label your axis, that graph doesn't say anything. 2. Maybe we should be looking at percentage change in the graph rather than whatever is being graphed here.
In context, the graph is intended to show the dominance of REST over time and not how it's losing out to any of the other items.
Re: REST API Alternatives
#5If he's making the claim that "there are a number of initiatives, technologies and discussions that are starting to nibble at the crust of the de-facto standard that REST has become.", then surely he would have evidence of this claim? To start with: 1. Label your axis, that graph doesn't say anything. 2. Maybe we should be looking at percentage change in the graph rather than whatever is being graphed here.
Relevant xkcd: http://xkcd.com/833/
Re: REST API Alternatives
#6If he's making the claim that "there are a number of initiatives, technologies and discussions that are starting to nibble at the crust of the de-facto standard that REST has become.", then surely he would have evidence of this claim? To start with: 1. Label your axis, that graph doesn't say anything. 2. Maybe we should be looking at percentage change in the graph rather than whatever is being graphed here.
In context, the graph is intended to show the dominance of REST over time and not how it's losing out to any of the other items.
If that's the case, then his paragraph after the graph is not backed up with any data.
Instead, to me, it seems like he's trying to justify that statement with a poor microsoft office graph.
Re: REST API Alternatives
#7Earlier quoted context omitted.
In context, the graph is intended to show the dominance of REST over time and not how it's losing out to any of the other items.
If that's the case, then his paragraph after the graph is not backed up with any data. Instead, to me, it seems like he's trying to justify that statement with a poor microsoft office graph.
The graph shows old techs that currently serve as more-or-less substitute goods for REST. He's saying the four items listed below have a much smaller or even tiny but, as of recently, nonzero following.
Re: REST API Alternatives
#8Answer: This isn't even applicable. REST is still a good tool that applies to many jobs, use it where it makes sense, don't use it where it doesn't.
Better title: "Is using REST for everything a bad idea perhaps?" Turns out that yes, yes it is.
Re: REST API Alternatives
#9Interesting 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.
Re: REST API Alternatives
#10If he's making the claim that "there are a number of initiatives, technologies and discussions that are starting to nibble at the crust of the de-facto standard that REST has become.", then surely he would have evidence of this claim? To start with: 1. Label your axis, that graph doesn't say anything. 2. Maybe we should be looking at percentage change in the graph rather than whatever is being graphed here.
In context, the graph is intended to show the dominance of REST over time and not how it's losing out to any of the other items.
What the fuck is JavaScript thing doing in there then?