3 ms·

Now that you mention this, it's interesting for me to consider in retrospect. At least one prior employer had me architect solutions that were designed around s

Now that you mention this, it's interesting for me to consider in retrospect. At least one prior employer had me architect solutions that were designed around scaling up using very small instances in large numbers during peak load. In theory those are deployed in the private address space behind a load balancer, but getting any actual information on the production deployment was like pulling teeth.

nine_k 3y ago
I've seen a similar setup ~12 years ago: a very elastic setup on AWS following load changes. At peak times, the clusters had substantially more than 1k API instances running together; none of the the API instances ever had a public address, and not for cost reasons. Everything was on EC2, behind a bastion; you had to jump through two jump hosts to SSH to particular boxes (containers were not a thing yet). Everything ran on private networks. Everything was exposed through load balancers (HAProxy) via 2 or 3 public IPv4 addresses; I think one of them was only to interact with an off-AWS third-party service over the public internet. Yes, it was a startup, just very technically-minded.