Yep, also GraphQL and all those data lakes.
That reminds me "XML is the future": https://www.bitecode.dev/p/hype-cycles
That reminds me "XML is the future": https://www.bitecode.dev/p/hype-cycles
And that won't change so long as object stores like S3 are so much cheaper.
And what exactly is wrong with GraphQL ? It is better than REST for a number of use cases.
When a response is a representation of a single resource, that response has a definitive caching lifetime. When a response represents a synthesis of a bunch of random crap the user asked for, the response has no clear caching lifetime, and so is uncacheable.
Most of the scalability the web has achieved, rides on the back of response caching at one level or another. Even low-level business-backend vendor APIs can—and are often designed under the assumption and requirement of—being cached. GraphQL throws that property away.
What's wrong with graphql is what's wrong with k8: people use it in the wrong context, and the right context is not most projects.