Question about GraphQL
I'm working on a fairly large (mobile app) project with a friend
The app itself is written in Kotlin and our backend service is written in C# using ASP.NET, we use EF Core to interact with our database, my friend has made a suggestion that we could use GraphQL for the backend service, now while I see the advantages that GQL could bring to the table I also see other things:
- lots of issues that GraphQL is supposed to solve feel like are already easily done with our EF Core structure or the Model structure in general
- users being able to request the data they Want sounds like a nightmare to me
- single endpoint for a project this large may serve lots of disadvantages over time specially since we'd basically throw out the whole API controller thing where we can easily manage what class does what
What do you guys think
The app itself is written in Kotlin and our backend service is written in C# using ASP.NET, we use EF Core to interact with our database, my friend has made a suggestion that we could use GraphQL for the backend service, now while I see the advantages that GQL could bring to the table I also see other things:
- lots of issues that GraphQL is supposed to solve feel like are already easily done with our EF Core structure or the Model structure in general
- users being able to request the data they Want sounds like a nightmare to me
- single endpoint for a project this large may serve lots of disadvantages over time specially since we'd basically throw out the whole API controller thing where we can easily manage what class does what
What do you guys think
