The author of this article argues that the current way of calling the server with REST API through central Angular services is not a good fit for Component-based architecture. They propose co-locating queries with view logic, using GraphQL to achieve this. The benefits include each component specifying its own data dependencies without knowing a central service or another parent component in the current render tree, fetching exactly the information that this Component tree needs in one single request, and exposing new fields without changing existing endpoints. This approach allows components to be reusable, self-contained, and adaptable to changes in their requirements. The article concludes by emphasizing that GraphQL can bring these benefits to Angular applications, alongside regular REST services, and notes several notable talks and resources on the topic.