This high-level task tracks the exploration and development of guidance for Apollo Client/Server enhancements. Expectations for all sub-tasks include:
- An ADR (Architecture Decision Record) must be created for each area explored to capture decision making, reasoning, and outcomes.
- The ShareThrift system may not have sufficient UI complexity to fully prove out all guidance; contributors are encouraged to create dedicated sample applications (e.g., a public GitHub repo) focused on complex or contrived scenarios relevant to their task's scope.
- Team may share these sample repos with the Apollo community (forums, Reddit, etc.) to solicit discussion and feedback before finalizing guidance. (After review with SMEs)
Areas to explore include UseFragment vs HTTP Batch/DataLoader, public caching strategies, server- and client-side caching, and the development of a proof-of-concept repo for complex GraphQL scenarios. See sub-tasks for detailed explorations.
This high-level task tracks the exploration and development of guidance for Apollo Client/Server enhancements. Expectations for all sub-tasks include:
Areas to explore include UseFragment vs HTTP Batch/DataLoader, public caching strategies, server- and client-side caching, and the development of a proof-of-concept repo for complex GraphQL scenarios. See sub-tasks for detailed explorations.