I don't know about Hashnode's case. But Twitter queries the database to create their feed/timeline for inactive users, so slightly slower than querying Redis.
I don't know about Hashnode's case. But Twitter queries the database to create their feed/timeline for inactive users, so slightly slower than querying Redis.
I don't know about Hashnode's case. But Twitter queries the database to create their feed/timeline for inactive users, so slightly slower than querying Redis.