You work on a mature web application that cleanly separates backend and frontend. The server-side code, written in Ruby, is mostly responsible for translating HTTP requests into SQL statements (with the help of an ORM) through rich and well-documented API. You choose GraphQL over REST to streamline your endpoints, but your database is not happy with all the extra queries. After much searching, you
![How to GraphQL with Ruby, Rails, Active Record, and no N+1—Martian Chronicles, Evil Martians’ team blog](https://cdn-ak-scissors.b.st-hatena.com/image/square/ead9807f2151cec346aa6ef9918575c997df6498/height=288;version=1;width=512/https%3A%2F%2Fevilmartians.com%2Fsocial-cards%2Fchronicles%2Fhow-to-graphql-with-ruby-rails-active-record-and-no-n-plus-one.jpg)