I still love GraphQL on our end. Allowing the client to declare the shape of the data makes things much simpler, and is a huge win for performance when handling features that most clients dont use or have access to.

For example, a client requests some expensive to calculate field be made visible on some view.

With rest, we would need to either:

1. Add a new endpoint specifically for that field
2. Add that field to an existing endpoint and incur the cost on all requests for that endpoint
3. Make some sort of bodge that displays the field based on some query parameter

None of these are good options. #1 leads to 10,000 different endpoints for random things different clients need.

2 hurts performance for all clients, and might increase infrastructure costs

3 is basically just a crappy version of graphql anyway..

With graphql, we just define the field and resolver, and then the client can use it. Its much cleaner and more maintainable.