Usage question: Http4k client. Any suggestions for managing
A) Retries on short periods of unavialble server/network (50x,)
B) "smart" cached dns ? -- aka a sort lived DNS cache that can be refreshed at interfals or after errors
--> By 'dns cache' I mean that a first level of resolution from 'name' to DNS occurs 'outside' -- the DNS name returned is not valid indefinately, is likely valid for hours or more but 'could' go away any second and need to get 'refreshed' via service discovery