Migrating to GraphQL: A Practical Assessment
I don&#x27;t think there&#x27;s any surprise that GraphQL reduces the size of the responses compared to typical REST (excluding things like JSON:API). If that&#x27;s the measurement that&#x27;s most important, then it seems GraphQL is the obvious choice.<p>For myself, the &#x27;practicality&#x27; of GraphQL would be more on complexity of the implementation, training of engineers, potential re-implementation of client logic, ease and depth of debugging, performance, etc. It seems these days that the size of the response is not typically a limiting factor in most applications I&#x27;ve interfaced with (though maybe I&#x27;ve never been exposed to that world before).<p>Can anyone speak to how a migration from REST to a GraphQL went? My biggest concern is around the complexity of the thing. It just seems so much more complex than REST, but maybe I haven&#x27;t spent enough time with it.