4 ms·
Like GraphQL, we just moved the integration and interface design complexity to the clients. Just publish your fucking read-only SQL credentials at this point.
by Mandatum 3y ago
Like GraphQL, we just moved the integration and interface design complexity to the clients.
Just publish your fucking read-only SQL credentials at this point.
- theK 3y agoTo be fair, GraphQL manages to reign in the ludicrussness that is exporting a read only SQL connection to levels that are merely unpredictable instead of outright dangerous. Still probably not the tech one needs. EDIT: add last paragraph
- Kwpolska 3y agoGraphQL does not prevent you or the GraphQL→DB translation layer from doing stupid things. Depending on the capabilities exposed by the GraphQL schema and the implementation of the translation layer, you can write a GraphQL query that is translated to 20 JOINs or N+1 hell or other bad things.
- hackandthink 3y agoGraphQL flexibility is fine but you need some discipline. We have been using GraphQL for 4 years and limit ourselves to queries with simple or medium complexity (no load the world, no problems).
- amq 3y agoThe end game is normal credentials with row level security.
- rzzzt 3y agoThat's OData: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752288 http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/comp...
- deleted 3y ago[deleted]