| ▲ | Lucasoato 6 hours ago |
| Hetzner is definitely an interesting option. I’m a bit scared of managing the services on my own (like Postgres, Site2Site VPN, …) but the price difference makes it so appealing. From our financial models, Hetzner can win over AWS when you spend over 10~15K per month on infrastructure and you’re hiring really well. It’s still a risk, but a risk that definitely can be worthy. |
|
| ▲ | mrweasel 3 hours ago | parent | next [-] |
| > I’m a bit scared of managing the services on my own I see it from the other direction, when if something fails, I have complete access to everything, meaning that I have a chance of fixing it. That's down to hardware even. Things get abstracted away, hidden behind APIs and data lives beyond my reach, when I run stuff in the cloud. Security and regular mistakes are much the same in the cloud, but I then have to layer whatever complications the cloud provide comes with on top. If cost has to be much much lower if I'm going to trust a cloud provider over running something in my own data center. |
|
| ▲ | adamcharnock 6 hours ago | parent | prev | next [-] |
| You sum it up very neatly. We've heard this from quite a few companies, and that's kind of why we started our ours. We figured, "Okay, if we can do this well, reliably, and de-risk it; then we can offer that as a service and just split the difference on the cost savings" (plus we include engineering time proportional to cluster size, and also do the migration on our own dime as part of the de-risking) |
|
| ▲ | wulfstan 4 hours ago | parent | prev | next [-] |
| I've just shifted my SWE infrastructure from AWS to Hetzner (literally in the last month). My current analysis looks like it will be about 15-20% of the cost - £240 vs 40-50 euros. Expect a significant exit expense, though, especially if you are shifting large volumes of S3 data. That's been our biggest expense. I've moved this to Wasabi at about 8 euros a month (vs about $70-80 a month on S3), but I've paid transit fees of about $180 - and it was more expensive because I used DataSync. Retrospectively, I should have just DIYed the transfer, but maybe others can benefit from my error... |
| |
| ▲ | adamcharnock 3 hours ago | parent | next [-] | | FYI, AWS offers free Egress when leaving them (because they were forced to be EU regulation, but they chose to offer it globally): https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-i... But. Don't leave it until the last minute to talk to them about this. They don't make it easy, and require some warning (think months, IIRC) | | |
| ▲ | wulfstan 2 hours ago | parent [-] | | Extremely useful information - unfortunately I just assumed this didn't apply to me because I am in the UK and not the EU. Another mistake, though given it's not huge amounts of money I will chalk it up to experience. Hopefully someone else will benefit from this helpful advice. |
| |
| ▲ | 2 hours ago | parent | prev [-] | | [deleted] |
|
|
| ▲ | baby 5 hours ago | parent | prev | next [-] |
| I’m wondering if it makes sense to distribute your architecture so that workers who do most of the heavy lifting are in hetzner, while the other stuff is in costly AWS. On the other hand this means you don’t have easy access to S3, etc. |
| |
|
| ▲ | iso1631 5 hours ago | parent | prev | next [-] |
| > I’m a bit scared of managing the services on my own (like Postgres, Site2Site VPN, …) Out of interest, how old are you? This was quite normal expectation of a technical department even 15 years ago. |
| |
| ▲ | christophilus 3 hours ago | parent | next [-] | | I’m curious to know the answer, too. I used to deploy my software on-prem back in the day, and that always included an installation of Microsoft SQL Server. So, all of my clients had at least one database server they had to keep operational. Most of those clients didn’t have an IT staff at all, so if something went wrong (which was exceedingly rare), they’d call me and I’d walk them through diagnosing and fixing things, or I’d Remote Desktop into the server if their firewalls permitted and fix it myself. Backups were automated and would produce an alert if they failed to verify. It’s not rocket science, especially when you’re talking about small amounts of data (small credit union systems in my example). | |
| ▲ | infecto 3 hours ago | parent | prev [-] | | No it was not. 15 years ago Heroku was the rage. Even the places that had bare metal usually had someone running something similar to devops and at least core infrar was not being touched. I am sure places existed but 15 years while far away was already pretty far along from what you describe. At least in SV. | | |
| ▲ | acdha 2 hours ago | parent [-] | | Heroku was popular with startups who didn’t have infrastructure skills but the price was high enough that anyone who wasn’t in that triangle of “lavish budget, small team, limited app diversity” wasn’t using it. Things like AWS IaaS were far more popular due to the lower cost and greater flexibility but even that was far from a majority service class. | | |
| ▲ | infecto 2 hours ago | parent [-] | | I am not sure if you are trying to refute my lived experience or what exactly the point is. Heroku was wildly popular with startups at the time, not just those with lavish budgets. I was already touching RDS at this point and even before RDS came around no organization I worked at had me jumping on bare metal to provision services myself. There always a system in place where someone helped out engineering to deploy systems. I know this was not always the case but the person I was responding to made it sound like 15 years ago all engineers were provisioning their own database and doing other times of dev/sys ops on a regular basis. It’s not true at least in SV. |
|
|
|
|
| ▲ | objektif 2 hours ago | parent | prev [-] |
| No amount of money will make me maintain my own dbs. We tried it at first and it was a nightmare. |
| |
