GraphQL is a comprehensive approach to guiding software developers in constructing data-driven applications. It is sometimes referred to be a platform or programming language agnostic query language. It is, in our opinion, the new API standard, allowing client applications to request particular data from the database rather than a full record. This article will teach you some of the core ideas needed to create a GraphQL API that uses Laravel.

We’re excited to announce that WSO2 API Manager 4.1—a complete platform for building, integrating, and exposing digital services as managed APIs in any environment—is now available. This release improves productivity in development and operations, expands support for different protocols and third-party technologies, and completes the product’s analytics story.

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.