3 ms·
It's not the cost of saving the resolved data. If I understand the pattern correctly, it is to avoid multiple asynchronous requests to a resource that has yet
by balls187 4y ago
It's not the cost of saving the resolved data.
If I understand the pattern correctly, it is to avoid multiple asynchronous requests to a resource that has yet to be cached.
- gorjusborg 4y agoYeah, that's my understanding too. It seems like an optimization to prevent lots of downstream requests that occur in rapid succession before the first request would have finished. I'd also suspect that the entry would be removed from the map on failure.