Two of my favorite things about GraphQL are: - It has a well-defined pattern/structure so you don't have to waste a bunch of time thinking/arguing about what y

Two of my favorite things about GraphQL are: - It has a well-defined pattern/structure so you don't have to waste a bunch of time thinking/arguing about what your REST endpoints look like. - It lends itself very nicely to automatic code generation for both frontend and backend, so you can define your API first and then build outward from there. This makes full-stack development a breeze. If you're working on a solo project and you're not sure if GraphQL is right for you, I would say definitely give it a shot. As with anything it takes a bit to really figure it out in your brain, but once you do, you wont regret it or ever want to look back.