[lifeisstillgood]

The main takeaway is that the questions searched for are so widely distributed that there is no need for a cache layer - they are nothing but long tail.

At that point there is no 'cloud' design that can help. Its either one database (or maybe just shard everything onto thousands of distributed nodes)

But the point I am trying to make is that kubernetes and microservices etc are based on idea of winners - power laws. One tweet everyone wants to read. One search term, one viral video.

Then again. This is just a question of taste - the taste of the dev lead. What (s)he feels is best approach. Take another company doing the same thing and different approach might emerge.

[pickledish]

I mean, kubernetes or microservices don’t care how the data reads are distributed, right? That problem is a database-level thing whereas k8s is infrastructure, you can run any kind of database with any kind of sharding you want on it. I feel like it might be more accurate to say something like “the value of caching is based on the idea of winners” for example

[lifeisstillgood]

Yes. I think basically I would not have done it like that but they did, it's wildly successful so fair play - it's taste that makes the difference