"You may want to enable earlyoom, so your whole server doesn't go down when a service goes bananas."

Another option is to run BSD to avoid the Linux oom issue

For example, I'm not using Hetzner but I run NetBSD entirely from memory (no disk, no swap) and it never "went down" when out of memory

Looks like some people install FreeBSD and OpenBSD on Hetzner

https://gist.github.com/c0m4r/142a0480de4258d5da94ce3a2380e8...

https://computingforgeeks.com/how-to-install-freebsd-on-hetz...

https://web.archive.org/web/20231211052837if_/https://www.ar...

https://community.hetzner.com/tutorials/freebsd-openzfs-via-...

https://www.souji-thenria.net/posts/openbsd_hetzner/

https://web.archive.org/web/20220814124443if_/https://blog.v...

https://www.blunix.com/blog/how-to-install-openbsd-on-hetzne...

https://gist.github.com/ctsrc/9a72bc9a0229496aab5e4d3745af0b...

If it is possible to boot Hetzner from a BSD install image using "Linux rescue mode"^1 then it should also possible to run NetBSD entirely from memory using custom kernel

Every user is different but this is how I prefer to run UNIX-like OS for personal, recreational use; I find it more resilient

1.

https://docs.hetzner.com/robot/dedicated-server/troubleshoot...

https://blog.tericcabrel.com/hetzner-rescue-mode-unlock-serv...

https://github.com/td512/rescue

https://gainanov.pro/eng-blog/linux/hetzner-rescue-mode/

https://docs.hetzner.com/cloud/servers/getting-started/rescu...

ChromeOS has an interesting approach to Linux oom issues. Not sure it has ever been discussed on HN

https://github.com/dct2012/chromeos-3.14/raw/chromeos-3.14/m...