The ultimate purpose of this card is to clarify what the sync as a framework concept will actually look like for end users/developers. One of the big reasons for this is to derisk the work in our other cards and ensure the engineering team and the stakeholders have a good understanding of how the work on the Data Sync Server Framework can be progressed. Some things we need to understand
- Architecture of the Framework/SDK
- How much granularity do we need in terms of libs/modules
- Where will the repo(s) live and how we will structure them
- How can we test these components in isolation and together
- How can we publish these components
- What does the component usage look like
- How to deploy code that uses these components
- What Node / NPM versions / environments can we support
- Can we support multiple server frameworks? for example Apollo Server supports express, hapi and Koa
|