3 ms·
Well, we could use SQL instead of GraphQL and would get much more freedom on the requests we could make. I supose that this was the idea of nicoJuicy.
by chmike 9y ago
Well, we could use SQL instead of GraphQL and would get much more freedom on the requests we could make. I supose that this was the idea of nicoJuicy.
- antonvs 9y agoThe problem with that is it assumes that there's no logic on the back end, outside the database, that transforms data before sending it to the client. If all you want is a way to submit SQL queries from a front end to a SQL database, you could just have the front end talk directly to the database. There's no need for a back end app in that case. But APIs are for talking to applications.
- tedmiston 9y agoIt also assumes all of the data is in one database. A common use case for GraphQL is to wrap multiple REST APIs and proxy calls to them as a "master API".
- watwut 9y agoSure. And you would also had much less control over access rights and such. You would have to implement everything in the database itself.