Nobody on my team will be in the same office. Almost all the folks I need to interact with on our current/future projects will be in different office.

I mentioned that in my comment. Maybe for someone like you it's enough to come twice a week. It's important for you to make connections with people in your org even if you're currently not working with them on the same project. Otherwise you end up with many silos which is bad for the company.

Yeah, all of those tools have APIs…

Small note - AWS Network Load Balancers maintain the same IP addresses.

That's true, but functionality-wise, they can do much fewer things.

With an application load balancer, you can set up multiple backends, do basic redirections, do OIDC authentication, etc.

With a network load balancer, you can only spread TCP and / or UDP connections.

Yeah I was confused too. Why on earth will someone provide a load balancer if it keeps changing it's IP address as it scales?

The normal AWS load balancers are set up to stay in service as long as the cache time on their IP address having been served by DNS... (which, FWIW, I have long argued "isn't sufficient", as many ISPs in countries half a world away from the US or using tech like satellites don't honor DNS cache times and then your requests end up getting routed to someone else... I routinely got tons of HTTP requests clearly destined for someone else's product).

Because they're intended to be referenced via hostname, and yes, regular HTTP AWS load balancers do indeed rotate their IPs.

The instance isn’t terminated (gone). It’s either shutdown or rebooted depending on the type of hardware failure.

It doesn't get transferred to a different physical instance, right?

I have never seen it migrated to a different instance type, but it would be running on a different physical server.

Why would anyone even care

I think many would make assumptions about the state of the instance and their application, which are likely to be wrong.

Some virtualization platforms support live migrations (hyper-v and ESXi), but this isn’t something AWS supports (afaik). Anytime your instance is stopped/started or rebooted then you may end up on a different physical host.

Having gone from a lot of C# to some Go, I’m use to passing in a CancellationToken to all asynchronous methods. I’ve noticed that there’s a lot of Go libraries missing Context support too .

As long as you’re not asking the same questions repeatedly, then you’re doing great! It’s important that you’re learning, growing, and asking new questions. Collaborating and asking for help is an important part of being a team.

Many people like being asked to help. I love giving my coworkers a second pair of eyes and helping them discover a solution to their problem. It’s incredibly rewarding and I’ll almost always learn something.