[derricgilling]

I prefer REST especially for public/external APIs. It's more empathetic towards third party developers who may not be as intimate with your API as your internal team. For example, much easier to reason a few well-understood entities like items, users, and orders if I was building an e-commerce API then a list of RPC operations. I would add GraphQL can also be easier to understand as long as the entity relations make sense. Lot's of exciting stuff happening in the GraphQL world but it does have disadvantages also.