Debugging APIs can be a challenge for any developer dealing with RESTful APIs. Trying to create an exact API request, especially for highly complex requests with large API request bodies and multiple headers, is essential but also tough to do. By using a tool like Postman to create a request for debugging purposes and as an API client, you can easily replay an API request with the exact configuration of the original request.
Have you ever faced the task of implementing a REST API and had to call multiple endpoints to populate data for a single screen? You probably wished you had more control over the data returned by the endpoint so that you could fetch more data with a single endpoint call or have only the necessary data fields returned by the call. Follow along to see how you can achieve this with GraphQL. In this article, we’ll be implementing GraphQL in an existing codebase.
In our previous post, we discussed the benefits and drawbacks of two of the most popular API models – REST and gRPC. In this post, we’ll highlight the final API model in our series, GraphQL. Finally, we’ll recap our learnings with a side-by-side comparison of REST, gRPC and GraphQL.
