Now that I've introduced to a good degree REST, GraphQL, and gRPC, a more objective comparison of the three can be made. As there are no silver bullets; each of the options will be evaluated against multiple criteria, aiming to cover key aspects of the API life cycle and architecture, such as developer experience from the perspective of both frontend and backend developers, common patterns, fitness, authentication and authorization, caching, and versioning.
The scoring is simple: just based on pluses (+) and minuses (-). Two pluses are the maximum score (++), indicating that the option delivers the best possible answer to a given criterion. The worst score is two minuses (--), indicating the opposite. When there aren't ...
