[archi42]

In essence, yes, but strictly speaking, no. Instead of caching responses, that layer seems to only bundle equal requests.

So once a request is sent to the database, every other instance of the same request (e.g. "hey, fetch me all messages from server id 42") is put on hold. Once the initial request gets an answer from the database, that answer is distrubuted to the inital requester and all those which were on hold. Now if someone is late to the party, they will initiate a new request to the database, because the response is not cached.

I really like this, and this a is great article to share on HN :)