graphql   6681

« earlier    

Gridsome - Build blazing fast websites with Vue.js and GraphQL
Use any CMS or data source for content. Pull data from WordPress, Contentful, local Markdown, or any other headless CMS or APIs and access it with GraphQL in your pages and components.
graphql  vue  static  generator  wordpress 
yesterday by to
Introducing GraphQL resolver tracing in AWS X-Ray – Life and Tech @ LifeOmic – Medium
Introducing GraphQL resolver tracing in AWS X-Ray - Added June 18, 2018 at 02:38PM
aws  aws-xray  graphql  read2of 
yesterday by xenocid
302 Found
Introducing the GraphQL Guide - Added June 15, 2018 at 03:40PM
books  graphql  read2of 
yesterday by xenocid
Build a Serverless GeoSearch GraphQL API using AWS AppSync & Elasticsearch
Build a Serverless GeoSearch GraphQL API using AWS AppSync & Elasticsearch - Added June 15, 2018 at 03:18PM
api  aws  aws-appsync  elasticsearch  graphql  read2of  serverless  tutorial 
yesterday by xenocid
The GraphQL Stack, explained
The GraphQL Stack, explained - Added June 15, 2018 at 02:58PM
graphql  read2of 
yesterday by xenocid
302 Found
Full Stack Error Handling with GraphQL and Apollo ? - Added June 14, 2018 at 02:38PM
api  graphql  javascript  read2of 
yesterday by xenocid
Staying on Top of Changes in GraphQL | GitHub Developer Guide
"Staying on Top of Changes in GraphQL
May 3, 2018 xuorig
To provide a more seamless experience we prefer to continuously evolve our schemas rather than using API versioning. Continuous evolution allows us to iterate faster and provide our integrators with new schema members more often. We do our best to avoid breaking changes, but sometimes it's necessary to offer an unversioned API.

We strive to provide the most stable APIs to our integrators and to provide transparency about new developments. This is why we recently shipped the brand new Breaking Changes page, which announces future breaking changes to our GraphQL schema.

Internally, our engineers mark certain schema members as deprecated using a Ruby API on top of the graphql-ruby gem. Using the changes metadata provided by our engineers, we automatically compute removal dates and generate this breaking changes page, meaning you'll always get up to date information."
github  graphql  versioning  schemas  apis  omgwtf 
yesterday by earth2marsh
Breaking Changes | GitHub Developer Guide
"Breaking changes are any changes that might require action from our integrators. We divide these changes into two categories:

Breaking: Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change.
Dangerous: Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change.
We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a schema preview.

We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st."
github  changes  apis  breaking  versioning  graphql  omgwtf 
yesterday by earth2marsh
GraphQL Best Practices | GraphQL
While there's nothing that prevents a GraphQL service from being versioned just like any other REST API, GraphQL takes a strong opinion on avoiding versioning by providing the tools for the continuous evolution of a GraphQL schema.

Why do most APIs version? When there's limited control over the data that's returned from an API endpoint, any change can be considered a breaking change, and breaking changes require a new version. If adding new features to an API requires a new version, then a tradeoff emerges between releasing often and having many incremental versions versus the understandability and maintainability of the API.

In contrast, GraphQL only returns the data that's explicitly requested, so new capabilities can be added via new types and new fields on those types without creating a breaking change. This has lead to a common practice of always avoiding breaking changes and serving a versionless API."
versioning  apis  graphql  schemas 
yesterday by earth2marsh
Goodbye REST APIs. Hello GraphQL!
Cory House discusses GraphQL, what makes it attractive, how GraphQL integrates with React, Angular, Vue and others, and how to migrate from REST APIs.
yesterday by geetarista
99designs/gqlgen: go generate based graphql server library
go generate based graphql server library. Contribute to 99designs/gqlgen development by creating an account on GitHub.
github  go  graphql 
yesterday by snahor
How to GraphQL - The Fullstack Tutorial for GraphQL
The Fullstack Tutorial for GraphQL - Added June 14, 2018 at 12:32PM
api  graphql  read2of 
yesterday by xenocid
302 Found
Deploy an AWS AppSync GraphQL API with CloudFormation - Added June 08, 2018 at 11:20PM
api  aws  aws-appsync  aws-cloudformation  graphql  read2of 
yesterday by xenocid

« earlier    

related tags

api  apis  apollo  authentication  aws-appsync  aws-cloudformation  aws-xray  aws  baas  backend  books  breaking  changes  client  cms  cons  cool-tools  cool  course  database  db  deployment  design  django  docker  documentation  drupal  drupal8  dynamic  elasticsearch  example  expressjs  frontend  gatsby  generator  github  go  golang  graphene  heroku  http  ifttt  javascript  js  library  omgwtf  openapi  opensource  pocket  postgres  postgresql  programming  pros  python  react  read2of  realtime  reasonml  reference  rest  ruby  sample  schema  schemas  server  serverless  slides  software-architecture  static-site-generator  static  subscription  testing  tools  tutorial  use  versioning  versus  vue  web-framework  web  webdesign  wesbos  wordpress 

Copy this bookmark: