Sharing Top Content from the Angular-sphere.

GraphQL the future for APIs?

  • GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data.
  • Your client requests data in one request even in slow mobile network connections.
  • There are a number of reasons you might use GraphQL in your product or project.
  • Rather than construct several REST requests to fetch data that you’re interested in, you can often make a single call to fetch the information you need.
  • We think though GraphQL is backed by big companies, thinking in Graphs seems to be good fit for your data and kind of topology.

There has been a lot of buzz about GraphQL recently. GraphQL name rings bell in most of conferences around the world. There were a number of GraphQL sessions in the recent ReactEurope tour. This post throws insights on why GraphQL is the future for APIs.

@ideas2it: GraphQL the future for APIs? Click on the link to know more.

#ideas2it #graphql #angularjs #javascript #facebook

There has been a lot of buzz about GraphQL recently. GraphQL name rings bell in most of conferences around the world. There were a number of GraphQL sessions in the recent ReactEurope tour. This post throws insights on why GraphQL is the future for APIs.

GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data. GraphQL isn’t tied to any specific database or storage engine and is instead backed by your existing code and data.

GraphQL is internally developed by Facebook in 2012 before being publicly released in 2015. GraphQL is a new way to think about building and querying APIs. Rather than construct several REST requests to fetch data that you’re interested in, you can often make a single call to fetch the information you need.

Why GraphQL?

There are a number of reasons you might use GraphQL in your product or project.

GraphQL’s query has exactly the same shape as the response.

GraphQL suggests to model your business domain as a graph by defining a schema and within that schema define your nodes and relationship between them.

Who is using GraphQL?

GraphQL is used by big companies and teams of all sizes.

There are various resources out in the Web to learn GraphQL. Start learning from the official GraphQL website. Learn GraphQL by Arunoda Susiripala is an excellent 10-part tutorial that teaches you the basics of GraphQL.

Looking for documentation on how to build a GraphQL service? There are libraries to help you implement GraphQL in many different languages. GraphQL makes it easy to build powerful tools like GraphiQL by leveraging your API’s type system.

Graph-based solutions are great opportunities to think about redesigning your API. We think though GraphQL is backed by big companies, thinking in Graphs seems to be good fit for your data and kind of topology. We need to start thinking above REST APIs to solve our business problems.

That’s it for now. Let us know what you think about GraphQL. If you have already tried out or plan to use in the next project?

GraphQL the future for APIs?

Comments are closed, but trackbacks and pingbacks are open.