2 ms·
GraphQL should die in the same hell with SOAP. For me 3 reasons "why not GraphQL" are: 1) Access control: rights, permissions, roles - they are just a fog when
by EugeneOZ 6y ago
GraphQL should die in the same hell with SOAP.
For me 3 reasons "why not GraphQL" are:
1) Access control: rights, permissions, roles - they are just a fog when client can write own query to DB.
2) Knowledge sharing: when your client knows too much about DB, you have a very tight coupling.
3) Complexity of the service layer. If there is no tool for the language you love - write your own GraphQL library. And there is no guarantee that your other client will be able to reuse this API.