@ni9elives@faizannriaz You are forgetting that we are discussing a public issue here. Not something that someone has done in private. When you speak like that in public, be ready to be corrected.
@aminnnn_09@ashoKumar89 I believe they store every view since they need it for watch history, including where a user stopped watching. But counting views by scanning that dataset would be expensive. They likely use algorithms like HyperLogLog to maintain a close estimate at scale.
@OraclingOerty@ni9elives@faizannriaz Two wrongs don't make it right. Please share some authentic reference that objecting any of ALLAH's attributes is allowed.
@devXritesh The first thing that will be under huge load is not the cache as pointed by others. It's your web server or your load balancer. This is the point of entry and if it receives a lot of requests at once, the queue will build up quickly and connection pool will be exhausted
@EOEboh There can be many reasons, simplest of them could be wrong credentials. There are other reasons of course like not being on the same network etc. Or the postgres container started but it's not ready for connections.
@ashoKumar89 People are mentioning cache stampede. However what if all those 100 requests are from different users i.e. userId is different in each request?