Originally Posted by
D582
REST isn’t going anywhere for a long time. And for many use cases it’s perfectly fine. (For example if all you need is a couple of GETs and POSTs with very narrow scope and very structured data then it’s fine).
But if your app needs to make multiple round trip calls to multiple URL endpoints and ends up receiving more data than it needs, GraphQL is much better suited and can be much more efficient.
Yep, agreed. Just because a technology is "old" does not necessarily make it "useless" or "outdated"... some don't get deprecated (even old versions) for decades. Many of my clients are fine with REST. Some don't even use REST and that's fine and dandy be them, as well as myself.
Besides, when we're talking about airlines, banks, old-blood companies, etc. that have been around for decades/centuries, there is a lot of "stuff" behind that scenes, including old but perfectly functioning systems that are often not worth it to replace... oh, and I'm also perfectly fine with recommending using JSON, REST, and other grandma technologies when the situation presents itself. All of my clients are perfectly happy with this... and tbh, these things are the least of their worries/problems.
(Before JSON became mainstream, I was using other very old-school techniques that are still in use today by past clients... to the, if it ain't broke, don't fix it)