Table of contents
Strongly Typed
GraphQL.js allows for strongly typed schemas, making it easier to perform validation and introspection on your data, ensuring that queries conform to a specific structure before execution.
Efficient Data Fetching
GraphQL.js enables clients to request exactly the data they need which can reduce over-fetching and under-fetching compared to REST APIs.
Rich Developer Tooling
The introspection capabilities in GraphQL.js allow for rich tooling, enabling better development workflows including robust IDE support and tools like GraphiQL.
Evolving APIs
GraphQL.js facilitates evolving APIs without the need for versioning, providing backward compatibility by introducing non-breaking changes.
Community Support
GraphQL.js has a large and active community, providing numerous resources, plugins, and tools that support smooth development processes.
We have collected here some useful links to help you find out if graphql.js is good.
Check the traffic stats of graphql.js on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of graphql.js on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of graphql.js's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of graphql.js on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about graphql.js on Reddit. This can help you find out how popualr the product is and what people think about it.
To begin, I'm going to start with GraphQL. This repo is a JS-specific implementation for GraphQL, for which projects written in JS/TS can utilize to build an API for their web app. The reason why I chose this project is because I've always been intrigued by how GraphQl challenges the standard way of building an API, a.k.a REST APIs. I have very little knowledge about this project since I've never used it before at... - Source: dev.to / over 2 years ago
When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus. Source: almost 3 years ago
GraphiQL (and many other tools) relies on introspection query which AFAIK is not guaranteed to have any specific order (and many libs don't support it). Apollo Server is built on top of graphql-js and it relies on it for this functionality. Source: over 3 years ago
Defining your schema and the resolvers simultaneously led to some issues for developers, as it was hard to decouple the schema from the (business) logic in your resolvers. The SDL-first approach introduced this separation of concerns by defining the complete schema before connecting them to the resolvers and making this schema executable. A version of the SDL-first approach was introduced together with GraphQL... - Source: dev.to / over 4 years ago
Graphql-yoga is built on other packages that provide functionality required for building a GraphQL server such as web server frameworks like express and apollo-server, GraphQL subscriptions with graphql-subscriptions and subscriptions-transport-ws, GraphQL engine & schema helpers including graphql.js and graphql-tools, and an interactive GraphQL IDE with graphql-playground. - Source: dev.to / over 4 years ago
The Engine (in the Javascript world the most popular one is graphql.js) should be responsible of taking a ready schema and resolvers, validate the objects, introspecting them and executing documents against them at runtime. - Source: dev.to / almost 5 years ago
One thing to understand is that, if you are using Node.js graphql-js would typically be the underlying implementation of all libraries and ultimately everything would get converted to JS/TS objects typically an AST ultimately making all these as abstractions on top of the existing way to define schemas. Note that the implementation can differ a bit in other languages or even within Node.js if you are using other... - Source: dev.to / almost 5 years ago
Power of a full language runtime like graphql-js. - Source: dev.to / over 5 years ago
Do you know an article comparing graphql.js to other products?
Suggest a link to a post with product alternatives.
Is graphql.js good? This is an informative page that will help you find out. Moreover, you can review and discuss graphql.js here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.
