That's exactly what I'm saying. If you have a web application with only one data source built in, then GraphQL is not for you. In fact, that whole post wasn't for you. You probably should stick with a monolith until you can't.

If you have a large, complex web application that integrates data from many different sources, then an API aggregator or view model is essential.

GraphQL is not an attempt to move the datastore clientside.