Session Cache Timing
crisward opened this issue · comments
If a user hits a server with lots of simultaneous quests, and the session in memory cache has expired, the cache gets updated for every request.
The first request should somehow get the others to wait until it has finished getting the data from the db, then respond to all of them from the cache to prevent the db being hit for every request. Perhaps in a similar way we do promise caching in node?