GraphQL puts the user in control of their own destiny. Yes, they are confined to your schema, but beyond that they can access the data in any which way. Will they ask only for the "events", or also for the "category" of each event? We don't really know! In REST based APIs we know ahead of time what will be rendered, and can plan ahead by generating the required data efficiently, often by eager-loa
![Efficient GraphQL queries in Ruby on Rails & Postgres](https://cdn-ak-scissors.b.st-hatena.com/image/square/28fcf26d7edbf533b637a96dc25acc5f57c9d198/height=288;version=1;width=512/https%3A%2F%2Fpganalyze.com%2Fstatic%2Fffb81b5dbfca4ab43d4387d338309b13%2Ffcb2f%2Fefficient_graphql_queries_in_ruby_on_rails_and_postgres_pganalyze.jpg)