3 ms·
1. graphql absolutely does not open you up to sql injection attacks. You could certainly end up being trapped by a endless recursive call loop but there are way
by cultofmetatron 4y ago
1. graphql absolutely does not open you up to sql injection attacks. You could certainly end up being trapped by a endless recursive call loop but there are ways to clip your tree to avoid that!
2. graphql does not force your business logic to the client. you write a mutation. it takes parameters. whatever goes on after that is in the server and is whatever you want ON THE SERVER.
disclaimer: I built my startup on graphql.
Their hyperlambda product seems interesting but the number of things they get flat out wrong about sql makes me question if they did their homework before trying to make something better.