500 Async Calls, One Number That Explains Why
DEV Community
500 Async Calls, One Number That Explains Why
I fanned out a batch job with Task.WhenAll and accidentally hit a downstream service with 500 simultaneous calls. Here's the one number that showed me the problem, and what capping concurrency actually costs.
0 comments
No comments yet.