Re:Acorn: A simple application deployment framework for Kube...
by nurettin on Sunday August 28, 2022 @01:35AM
(#32626048)
Set up large baremetal so that you don't have to scale for a long time and by the time you do, you have had your first million users and you can afford spending for inanely complex infra and don't care about aws billing anymore. Set up user services with systemctl, access your logs through journalctl, change your configs with rsync. And op was arguing against the cloud so giving cloud examples is beside the point. No need for all the sass.
[ Parent
| on HN ]
Re:Acorn: A simple application deployment framework for Kube...
by jb_gericke on Sunday August 28, 2022 @02:24AM
(#32626236)
And when your one big server fails and your first million customers start looking for more stable alternatives?
Re:Acorn: A simple application deployment framework for Kube...
by v3ss0n on Sunday August 28, 2022 @05:30AM
(#32626981)
One big server ( 6 Physical Core Xeon with 64GB of Ram , 1TB Nvme SSD) only cost 80$ a month .
Can start with 2-3 big servers across 3 different DC. Equlivant specs would cost easily 300$ a month on AWS/GCP/Azure .
Re:Acorn: A simple application deployment framework for Kube...
by nurettin on Sunday August 28, 2022 @02:40AM
(#32626310)
Then you have a few hours of downtime. Happens to the best of us.
Re:Acorn: A simple application deployment framework for Kube...
by thejosh on Sunday August 28, 2022 @06:45AM
(#32627300)
Because all the cloud providers never have downtime, DNS issues, etc? :)
At least when US east is down, half the internet is down.
Re:Acorn: A simple application deployment framework for Kube...
by RaitoBezarius on Sunday August 28, 2022 @08:54AM
(#32628051)
Then, you had disaster recovery plans, you devised a strategy of what is an acceptable data loss, execute the reconstruction plan on the new big server, under some hours, the new big server is up again.
You apologize, offer some financial compensation, etc.
And you learn from the situation, understand what are your new tolerance for data loss, failures, etc., then start new plans accordingly.