[nullpoint420]

Yeah I mean sunk cost fallacy, right? If you’ve already hit critical mass in AWS of course you’re going continue investing in it.

If I were to be CTO of a brand new company today, I’d probably just colocate my own servers with K8S. Much cheaper and much lower latency. 2x 1TB RAM servers with 3x 8TB high speed U.2/U.3 drives each would last years.

[nine_k]

What is your plan when one of the machines needs to be taken offline for repairs? The probability is low, but the downside may be large.

[nullpoint420]

Take it down and replace it? Obviously I’d have HA setup between my nodes, with CSI replication.

If budget allowed, I’d even spin up another region with DB failover setup too.

All the same architecture applies, the only difference is it’s done with K8S yaml instead of the CDK

[tardedmeme]

How would you do that on AWS? They can shut down your VM due to hardware failures on the host. The probability is low, but the impact may be large.

[nine_k]

(1) They will usually notify a few minutes (or hours) in advance, and (2) it would take a few minutes to spin up and set up a new VM to replace the old, without leaving your terminal.

[throawayonthe]

have three of them

[nullpoint420]

Haha exactly - or 4 if we’re balling