Saving on egress switching from AWS to Hetzner

Re:Saving on egress switching from AWS to Hetzner by bpodgursky on Monday January 24, 2022 @11:55PM (#30068212)

Nobody said you can't operate with old-style VMs and ansible or puppet or whatever, but tbqh yes, you're going to move slower.

It may not be fatal to your business; it's not going to be a top 3 reason you succeed or fail! But it does make a difference.

[ Parent | on HN ]

Re:Saving on egress switching from AWS to Hetzner by funcDropShadow on Tuesday January 25, 2022 @02:54AM (#30069329)

> Nobody said you can't operate with old-style VMs and ansible or puppet or whatever, but tbqh yes, you're going to move slower.

To stay in your metaphor, moving faster is not a guarantee to arrive at your target earlier. As long as everything works fine, using k8s is great. When you have to dig deep to solve a problem, a stack with less layers might be a huge advantage.

[ Parent | on HN ]

Re:Saving on egress switching from AWS to Hetzner by guiriduro on Tuesday January 25, 2022 @03:52AM (#30069710)

Sounds like you moved your complexity from machine virtualization to container orchestration. Doesn't sound like you won anything, least of all agility.

[ Parent | on HN ]

Re:Saving on egress switching from AWS to Hetzner by robrorcroptrer on Tuesday January 25, 2022 @03:20AM (#30069498)

Is everything about to move fast? When you read a book, is it a race to get to the last page? When you sing a song, is the goal to get to the last word as soon as possible?

[ Parent | on HN ]

Re:Saving on egress switching from AWS to Hetzner by krageon on Tuesday January 25, 2022 @06:17AM (#30070568)

If you'd do it for an employer, the answer to all these questions is yes.

[ Parent | on HN ]