It's refreshing that the author acknowledges the nuances around tradeoffs of using, and not using, GraphQL.
Having used REST (with swagger/openAPI), gRPC and now graphQL, the most painful thing has been the tribal militance from supporters of each, defending their own vested interest.
It's almost like different tools are useful for different things.
Having used REST (with swagger/openAPI), gRPC and now graphQL, the most painful thing has been the tribal militance from supporters of each, defending their own vested interest.
It's almost like different tools are useful for different things.