Closed subesokun closed 5 years ago
I'd use graphQL for interacting with the pricing API and REST to save/load the user assets, which should happen only once for a session. Agree?
Mhh personally I'd use it for both and depending and the current view only a subset of the user assets might be loaded to improve the initial page load, especially on flaky networks. But as I don't know yet which data gets transferred when loading the user assets I can't say that for sure. Also maintaining and documentating two APIs might be a bit troublesome.
🚮
For the frontend API we should use GraphQL and connect the resolvers to the Azure storage.