GraphQL
- GraphQL TSC Election Resultsgraphql.org GraphQL TSC Election Results | GraphQL
A query language for your API — GraphQL provides a complete description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.
- Announcing the GraphQL Foundation's Grant Awardees: Benefitting a GraphQL Ecosystem for Allgraphql.org Announcing the GraphQL Foundation's Grant Awardees: Benefitting a GraphQL Ecosystem for All | GraphQL
A query language for your API — GraphQL provides a complete description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.
- The Hidden Performance Cost of NodeJS and GraphQLwww.softwareatscale.dev The Hidden Performance Cost of NodeJS and GraphQL
NodeJS and GraphQL are popular technologies for building web applications, but in my experience, they come with certain scaling and performance tradeoffs to be aware of. tl;dr: GraphQL's modular structure generally leads to code that instantiates excessive promises, which degrades request performanc...
- where to implement directive logic
Hello! I was writing a hobby graphql project just to get a better grasp on it and am using the Lacinia clojure library. It’s directive documentation isn’t very fleshed out and I was wondering where directive logic generally takes place. I am using it with the pedestal library and was going to just write an interceptor after the query is parsed but was wondering if it was more standard to have it take place in the resolver logic or something. Thanks :)
