Not the GP but they might be referring to [0] or one of several other articles you will find if you Google "handle a million connections in *".
Realistically you also usually need to perform some non-trivial work from time to time for some non-trivial portion of those connections, which will further load your server, but still.
Genuinely curious on this—with port numbers only being 16 bits, how is it possible for one machine to ever handle more than 65k concurrent connections?
Connections must have unique IP:Port pairs between client and server. You're limited to 65K concurrent connections for the same client. In practice, no one is opening that many connections from a single client.
As such, the load balancer itself can probably hold a group of source IPs to use as second-hop solution to this problem as well if we're sincerely talking about load balancers holding a ton of largely idle connections simultaneously.
The more likely load balancer outcome would be DNS split on inbound client IPs, and scaling out until each load balancer handles the appropriate amount of traffic (by some measure and scale out if exceeded).
We already had a good sneak peek in Germany, when schools closed last year for some weeks due to the pandemic.
Popular video conferencing solutions weren't allowed due to privacy issues. The official "Lernraum" platform that have been used for this did not work most of the time.
I understand where these laws come from, but it's sad that there often is no European alternative
Thank God we have very capable cloud providers in Europe that will rise to the challenge and offer a viable opportunity to the US major cloud providers!
We definitely do have all of those. For some reason, IT managers prefer to teach themselves the AWS/Azure/GCloud configuration clusterfuck rather than the portable OpenStack configuration clusterfuck, but that's suffering we're all bringing on ourselves.
