Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Build institutional knowledge about GraphQL
  • Understand Better understand adoption requirements
    • Code complexity
    • Configuration changes
    • Performance
    Assess whether GraphQL is worth implementing within our APIs
    • If yes, make an adoption plan
    • If no, document why
    • If not sure, determine next steps for reaching certaintyWhat API conventions will help us be forwards compatible?
    • How should we structure front end state/logic code to be forwards compatible?

Plan

Developers involved in the spike will regularly share updates with the rest of the arch squad and pull in additional muscle as necessary. When the spike is completed, folks involved on the spike will present their findings to the squad and the squad will make an assessment as to whether GraphQL is worth adopting. The squad will present this assessment to the organization at large via arch lunch and eng demo/all hands.

...