Hacker News Reader

In Husky, how do you maintain very short cache times in your Writers without blowing up your S3 write costs?

It’s (very lightly) hinted at in the blog post (the section where we discuss “shard router”), but basically data locality in our pipelines by tenant + a little bit of buffering goes a long way.

I’m hoping I can coax one of my colleagues who works on the routing side of things to write a detailed blog post on just that topic though :)

That would be great! Really appreciate your write up, this space is really fascinating. The short cache / no stateful Writer / no searches on Writers thing stood out to me as a key differentiator to something like Grafana Loki.

Reply on news.ycombinator.com