Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More

TL;DR : I did not read the fucking manual.
Story :
We have a particular kind of setup with Blazor Server-side. And it does not use any SQL, bbut calls APIs.
The class to call APIs was scoped to create one new HTTP connection per new tab (even if the user opens a new tab, it's a new HttpClient).
We were fine. I read that we have 65k ports and disposal takes around 2 minutes, and we have around 1000 users. So it went into the "backlog, where things go to die."
Hard core duiscovery in the past 2 days.
Azure service plan for webapps only allows you 128 outbound connections!
System, we reboot it manually every 4 hours, while I'm working to make HttpClient unique lol
I just needed a break and vent. And "Hey kids, know that Azure service plan is only 128 sockets, not 65536."
rant