> There’s almost no overlap between SOAP and GraphQL oh they're entirely similar - overly complex data transfer schemes. They both also push too much respons

> There’s almost no overlap between SOAP and GraphQL oh they're entirely similar - overly complex data transfer schemes. They both also push too much responsibility on to the client. They also have steep learning curves. It may have started at facebook, but the graphql industry has a life of its own now. I've seen this with many technologies. People start tooling and consulting companies around some technology and start pushing it hard. If it isn't needlessly complex, why does it have its own conference? https://goodapi.co/blog/rest-vs-graphql https://goodapi.co/blog/rest-vs-graphql https://news.ycombinator.com/item?id=17565508 https://news.ycombinator.com/item?id=17565508 https://blog.hitchhq.com/graphql-3-reasons-not-to-use-it-7715f60cb934 https://blog.hitchhq.com/graphql-3-reasons-not-to-use-it-771... https://www.reddit.com/r/javascript/comments/ifxvo0/why_i_dont_use_graphql_anymore/g2qo5s1/ https://www.reddit.com/r/javascript/comments/ifxvo0/why_i_do...