Does multiple instance of httpClient inside an angular app will use multiple port? (angular)

Recently i learnt, its best advice to always create single instance of httpClient and reuse it for service lifetime in-order to avoid socket exhaustion, which makes sense, this got me think, in my angular projects at work, we have multiple service files where in constructor we initialize httpclient newly and consume it, and during run time there are components where multiple services are injected which means

Q1 . if multiple service are injected into a component and if those components have new instance of httpclient initialized at their constructor does that mean, at run time i will have 2 unique httpclient instance which can occupy 2 different port?

Q2. if yes should i still follow singleton pattern in front end?

Q3. I also read somewhere browser treats each tab as separate application so each tab can potentially occupy new port, is it safe to generalize it like this or there are edge cases which i need to be aware off.

Continue reading...