←back to thread

Use One Big Server (2022)

(specbranch.com)
343 points antov825 | 2 comments | | HN request time: 0s | source
Show context
runako ◴[] No.45085915[source]
One of the more detrimental aspects of the Cloud Tax is that it constrains the types of solutions engineers even consider.

Picking an arbitrary price point of $200/mo, you can get 4(!) vCPUs and 16GB of RAM at AWS. Architectures are different etc., but this is roughly a mid-spec dev laptop of 5 or so years ago.

At Hetzner, you can rent a machine with 48 cores and 128GB of RAM for the same money. It's hard to overstate how far apart these machines are in raw computational capacity.

There are approaches to problems that make sense with 10x the capacity that don't make sense on the much smaller node. Critically, those approaches can sometimes save engineering time that would otherwise go into building a more complex system to manage around artificial constraints.

Yes, there are other factors like durability etc. that need to be designed for. But going the other way, dedicated boxes can deliver more consistent performance without worries of noisy neighbors.

replies(11): >>45086252 #>>45086272 #>>45086760 #>>45087388 #>>45088476 #>>45089414 #>>45091154 #>>45091413 #>>45092146 #>>45092305 #>>45095302 #
Spooky23 ◴[] No.45089414[source]
It really depends on what you are doing. But when you factor the network features, the ability to scale the solution, etc you get alot of stuff inside that $200/mo EC2 device. The product is more than the VM.

That said, with a defined workload without a ton of variation or segmentation needs there are lots of ways to deliver a cheaper solution.

replies(1): >>45089477 #
troupo ◴[] No.45089477[source]
> you get alot of stuff inside that $200/mo EC2 device. The product is more than the VM.

What are you getting, and do you need it?

replies(1): >>45089746 #
throwaway7783 ◴[] No.45089746[source]
Probably not for $200/mo EC2, but AWS/GCP in general

* Centralized logging, log search, log based alerting

* Secrets manager

* Managed kubernetes

* Object store

* Managed load balancers

* Database HA

* Cache solutions

... Can I run all these by myself? Sure. But I'm not in this business. I just want to write software and run that.

And yes, I have needed most of this from day 1 for my startup.

For a personal toy project, or when you reach a certain scale, it may makes sense to go the other way. U

replies(4): >>45090159 #>>45090268 #>>45090516 #>>45094149 #
doganugurlu ◴[] No.45090159[source]
You need database HA and load balancers on day 1?

You must be doing truly a lot of growth prior to building. Or perhaps insisting on tiny VMs for your loads?

replies(2): >>45090357 #>>45103423 #
1. swiftcoder ◴[] No.45090357[source]
> Or perhaps insisting on tiny VMs for your loads?

This happens way too often. Early-stage startups that build everything on the AWS free tier (t2.micro only!), and then when the time comes they scale everything horizontally

replies(1): >>45103446 #
2. throwaway7783 ◴[] No.45103446[source]
I'll repeat what I said above. It's for availability (aka I don't want my customers screaming at me if the machine goes down). And no , scaling out was not our first solution, scaling up was. I have considered going bare metal so many times, but the number of things we need to build/manage by ourselves to function is too much right now.

Hopefully when we can afford to do it, we will.