As far as I can tell, I agree. An API is like a promise. In the best case, people decide to use your API and build on it. Then, if for whatever reason and in

As far as I can tell, I agree. An API is like a promise. In the best case, people decide to use your API and build on it. Then, if for whatever reason and in whatever way, you break your API, you force everyone affected to reimplement at least to some degree. With GraphQL you’ll be promising the sun the moon and the stars if you aren’t very careful. (Even if you are very careful you’re still promising a lot, though hopefully the available tools will help you out.) With GraphQL you put yourself in a very tough position of either keeping big promises or breaking big promises. Most of the time you are going to be better off keeping small promises.