-
GraphQL: the enterprise honeymoon is over 2025
- your GraphQL layer still has to overfetch from downstream REST APIs, then reshape the response. You didn’t eliminate overfetching. You just moved it down a layer
- observability is worse by default
- With GraphQL, a 200 can still mean partial or full failure.
- learning curve creates friction, especially when teams need to move fast. REST is boring, but boring scales extremely well.
- error handling is harder than it needs to be
-
Tech Dive - APIs REST Vs GraphQL
- Very short summary
-
GraphQL vs. REST APIs: Why you shouldn’t use GraphQL
- todo
Why not use GraphQL? - "I think GraphQL will change the world"
https://github.com/thoughtbot/guides/tree/master/graphql https://medium.com/codingthesmartway-com-blog/rest-vs-graphql-418eac2e3083 https://book.graphqlschemadesign.com/ https://www.howtographql.com/basics/1-graphql-is-the-better-rest/ https://blog.logrocket.com/5-reasons-you-shouldnt-be-using-graphql-61c7846e7ed3/
-
GraphQLize - A JVM library for developing GraphQL API instantly from Postgres and MySQL databases
-
SQL is a better API language than GraphQL. Convince me otherwise!
-
Graphene python GraphQL
https://productionreadygraphql.com/blog/2020-05-21-graphql-to-sql