GraphQL to EF & SQL Calls: https://github.com/EntityGraphQL/EntityGraphQL
Explanation from IBM
REST: CRUD based on resources. It provides complete set of operations over your data. But as a drawback in complex situations may send you over-fetched or under-fetched data.
GraphQL: To fetch or mutate data using exact one request. Schema+resolver you created will take care of the rest. Good in complex data situations or in situations when you want to reduce the throughput because of over-fetching.
GraphQL also does not dicrate patterns or project structure and could be introduced on top of already existing architecture.
Mutations (in my example you need to define what you expect in output because I return back Course from Repository):
