Change Details

Brain dump * timeout * custom user agent incl. version information of the termbox system performing the request (feature creep?) * caching * in-process caching of e.g. messages => !!question to ops: how many instance are we going to have, does it make sense to redundantly cache in (all the) processes or should we aim for a distributed cache instead?!! * response health stats (also to allow us to explain SSR's response times [given we can't be quicker than the APIs we depend on])? !!question to ops !! Notes: * there is a [[ https://www.npmjs.com/package/axios-cache-adapter | axios cache adapter ]]

Brain dump * timeout * custom user agent incl. version information of the termbox system performing the request (feature creep?) * caching * in-process caching of e.g. messages => !!question to ops: how many instance are we going to have, does it make sense to redundantly cache in (all the) processes or should we aim for a distributed cache instead?!! * response health stats (also to allow us to explain SSR's response times [given we can't be quicker than the APIs we depend on])? !!question to ops !! Notes: * there is a [[ https://www.npmjs.com/package/axios-cache-adapter | axios cache adapter ]] * there is also [[ https://github.com/kuitos/axios-extensions | axios-extensions ]]

Brain dump * timeout * custom user agent incl. version information of the termbox system performing the request (feature creep?) * caching * in-process caching of e.g. messages => !!question to ops: how many instance are we going to have, does it make sense to redundantly cache in (all the) processes or should we aim for a distributed cache instead?!! * response health stats (also to allow us to explain SSR's response times [given we can't be quicker than the APIs we depend on])? !!question to ops !! Notes: * there is a [[ https://www.npmjs.com/package/axios-cache-adapter | axios cache adapter ]] * there is also [[ https://github.com/kuitos/axios-extensions | axios-extensions ]]