3 ms·
There’s almost no overlap between SOAP and GraphQL (еxcept that you seem to not be familiar with either of them). Especially odd is the "scalability" remark, g
by slver 5y ago
There’s almost no overlap between SOAP and GraphQL (еxcept that you seem to not be familiar with either of them).
Especially odd is the "scalability" remark, given those are protocols, they have no bearing on any aspect of the "scalability" of the implementation that I can think of.
Actually both SOAP and GraphQL are often used as aggregate endpoints for exposing internal APIs, often for the infrastructure of entire companies (see how GraphQL is used at Netflix for example). So they're predominantly used where you NEED scale, and REST fails them, due to the heterogenous nature of their clients (external and internal) vs. the "prebaked" structure of REST as a large-grain resource protocol (Fielding's words, not mine).
And the "companies that profit from complex solutions" is a rather poor theory. GraphQL was designed by Facebook, which doesn't profit from "complex solutions". Quite the opposite, they want APIs that are accessible both to their teams and the world. Same with Netflix. GitHub. Shopify. Airbnb. PayPal.
Where are those evil companies conspiring to profit from complexity?
- fnord77 5y ago> 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...
- slver 5y agoYeah I got that you think they're "overly complex" but they literally have nothing to do with each other. REST is simple compared to GraphQL if you have no standards at all and just slap everything with ad-hoc CRUD resources at will. That's what you do, don't you? Ever tried to implement OData or OpenApi or any kind of structured API covering HATEOAS at all? Do you actually define your own content types, with MIME and so on? My guess is no. You're not doing REST. You're doing JSON CRUD RPC. REST is a quagmire of competing half-completed standards trying to do what GraphQL does in one step and with least amount of "maybe this maybe that" situations.
- jlouis 5y agoGraphQL is like 3k to 4k Lines in the server side. Not exactly a large system.