4 ms·
> Our crypto APIs are currently powered Finage.co.uk. We do some level of caching on our side but only for 5-10 mins. This seems very much at odds with the des
by jagger27 4y ago
> Our crypto APIs are currently powered Finage.co.uk. We do some level of caching on our side but only for 5-10 mins.
This seems very much at odds with the description of "up to the second cryptocurrency prices, quotes, previous close information, and news."
I wouldn't want to act on stale information, especially when the timestamp is truncated so much.
crypto/handler/crypto.go:172:
rsp.Date = time.Unix(0, int64(res.Timestamp)*int64(time.Millisecond)).UTC().Format("2006-01-02")
I understand the need for caching, of course.
- asim 4y agoI think you'll find most providers are doing some form of caching but I understand your point. We shouldn't miss sell it. Thanks for the feedback. I'd like to try provide up to the second relevant data but it would have to come from an exchange like binance or something else.
- gabereiser 4y agoWhat about utilizing your own pubsub to enable a websocket subscription to price pushes? You could still cache historic, folks can subscribe to events, charged for receipt? I don’t know how you have your backends but I wrote a trading platform once and this was how we did it. Don’t become a trading platform. Just provide a way to get the true latest quote if someone needs it.
- asim 4y agoVery interesting idea. I think a lot of people are asking for pubsub/events/websockets for updates on a number of APIs so if we can offer some sort of general abstraction to get events for any API that would be useful.